Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 09:46 UTC

rust-lang / futures-rs

Zero-cost asynchronous programming in Rust

RustApache-2.0★ 5,922 stars⑂ 707 forkssince Mar 2016View on GitHub ↗

rust-lang/futures-rs holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (83/100) and lowest on Security (66/100). It was last updated 7 days ago. 2 contributors account for most of its recent work.

92
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

92
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 78 is calibrated to 92 on the published index scale (record calibration 2026-08-02).

Ownership

The Rust Programming LanguageOrganization · verified domain
18,302 followers246 public repossince Sep 2013

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iofutures0.3.3456,136,4517535 days agoasyncfuturefuturesasynchronous
crates.iofutures-io0.3.3464,656,5304035 days ago—
crates.iofutures-core0.3.3474,762,4723935 days ago—
crates.iofutures-sink0.3.3468,181,7123935 days ago—
crates.iofutures-task0.3.3474,031,8423635 days ago—
crates.iofutures-test0.3.34299,5103635 days ago—
crates.iofutures-util0.3.3474,306,4513935 days ago—
crates.iofutures-macro0.3.3461,485,1103535 days ago—

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

77Good · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
9.7/36Commit cadence — 14/52 weeks with commits
15.8/18Commit volume — 56 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year56
human_commit_share0.92
days_since_last_push7
active_weeks_last_year14
How it's scored
27/27Ships releases — 68 releases published
36/36Release recency — latest release 35 days ago
12.6/27Release cadence — a release every ~154.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count68
latest_release_tag0.3.34
releases_from_tagsno
days_since_latest_release35
mean_days_between_releases154.6
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

80Excellent · 17% of overall
How it's scored
60/60Stars — 5,922 stars
23.7/25Forks — 707 forks
10.9/15Watchers — 94 watchers
Inputs used
forks707
stars5,922
watchers94
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 473,860,078 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesfutures, futures-io, futures-core, futures-sink, futures-task, futures-test, futures-util, futures-macro
dependents—
ecosystemscrates
total_downloads6,030,855,628
monthly_downloads473,860,078
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

83Excellent · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.3/22.5Commit distribution — top contributor authored 36% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 63 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled99
top_contributor_share0.363
How it's scored
34.5/42Issue resolution — 82% of issues closed
25.8/30PR acceptance — 1,553/1,805 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 3/10 approved changesets -- score normalized to 3
Inputs used
merged_prs1,553
open_issues211
closed_issues967
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.821
closed_unmerged_prs252
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 18,302 followers of rust-lang
25/25Track record — 246 public repos, account ~13 yr old
Inputs used
followers18,302
owner_typeOrganization
is_verifiedyes
owner_loginrust-lang
public_repos246
account_age_days4,753

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 8 package(s) on crates
35/35Publish recency — latest publish 35 days ago
20/20Version history — 75 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesfutures, futures-io, futures-core, futures-sink, futures-task, futures-test, futures-util, futures-macro
ecosystemscrates
any_deprecatedno
min_days_since_publish35

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .rustfmt.toml, Cargo.toml ([workspace.lints]), futures-channel/Cargo.toml ([lints]), futures-core/Cargo.toml ([lints]), futures-executor/Cargo.toml ([lints]), futures-io/Cargo.toml ([lints]), futures-macro/Cargo.toml ([lints]), futures-sink/Cargo.toml ([lints]), futures-task/Cargo.toml ([lints]), futures-test/Cargo.toml ([lints]), futures-util/Cargo.toml ([lints]), futures/Cargo.toml ([lints])
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://rust-lang.github.io/futures-rs/
10/10Repository description
10/10Topics — 1 topics
0/10Wiki
Inputs used
topicsasync-foundations
has_wikino
homepagehttps://rust-lang.github.io/futures-rs/
docs_sitehttps://rust-lang.github.io/futures-rs/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 3/10 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 63 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.5
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
12.3/35Direct dependencies free of known advisories — 1 affected: tokio 0.1.22 (high 8.1)
4/25Indirect dependencies free of known advisories — 16 affected: crossbeam-utils 0.7.2 (high 8.1), lock_api 0.3.4 (moderate 5.5), memoffset 0.5.6 (moderate), +13 more
15.4/40No advisories left outstanding — 17 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,328 days ago
Inputs used
sourceosv
advisories25
affected_packages17
assessed_packages72
unassessed_packages0
affected_by_severityhigh 2, moderate 2, unknown 13
direct_affected_packages1
Matched the crates:futures@0.3.34 runtime dependency closure — what installing the published package pulls in — 72 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

72Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
38.8/40Legible commit history — 67 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.728
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml, examples/functional/Cargo.toml, examples/imperative/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — .rustfmt.toml, Cargo.toml ([workspace.lints]), futures-channel/Cargo.toml ([lints]), futures-core/Cargo.toml ([lints]), futures-executor/Cargo.toml ([lints]), futures-io/Cargo.toml ([lints]), futures-macro/Cargo.toml ([lints]), futures-sink/Cargo.toml ([lints]), futures-task/Cargo.toml ([lints]), futures-test/Cargo.toml ([lints]), futures-util/Cargo.toml ([lints]), futures/Cargo.toml ([lints])
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 8 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, examples/functional/Cargo.toml, examples/imperative/Cargo.toml, futures-channel/Cargo.toml, futures-core/Cargo.toml, futures-executor/Cargo.toml, futures-io/Cargo.toml, futures-macro/Cargo.toml, futures-sink/Cargo.toml, futures-task/Cargo.toml, futures-test/Cargo.toml, futures-util/Cargo.toml, futures/Cargo.toml, futures/tests/macro-reexport/Cargo.toml, futures/tests/macro-tests/Cargo.toml, futures/tests/no-std/Cargo.toml
dependency_bot_commit_share0.08
How it's scored
45/45Type-checkable code — Rust (statically typed)
54.6/55Manageable file sizes — 2/306 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes88,421
source_files_sampled306
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

5,922GitHub stars
99contributors
56commits, last 12 months
7days since last push
68releases
2bus factor
211open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 707 ⇿
0Stars
707Forks
68Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0125250375500625750699212016-062021-072026-09
Major 0Minor 2Patch 46

Each point covers 10 days.

OpenSSF Scorecard 7.5 / 10
7.5aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-16 09:46 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 3/10 approved changesets -- score normalized to 3
10Contributorsproject has 63 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 36
RegistryPackageVersion constraintManifest
crates.iofutures-core=1.0.0-alpha.0futures-channel/Cargo.toml
crates.iofutures-sink=0.4.0-alpha.0futures-channel/Cargo.toml
crates.ioportable-atomic1.3futures-core/Cargo.toml
crates.iofutures-core=1.0.0-alpha.0futures-executor/Cargo.toml
crates.iofutures-task=0.4.0-alpha.0futures-executor/Cargo.toml
crates.iofutures-util=0.4.0-alpha.0futures-executor/Cargo.toml
crates.ioproc-macro21.0.60futures-macro/Cargo.toml
crates.ioquote1.0futures-macro/Cargo.toml
crates.iosyn3.0futures-macro/Cargo.toml
crates.iofutures-core=1.0.0-alpha.0futures-test/Cargo.toml
crates.iofutures-task=0.4.0-alpha.0futures-test/Cargo.toml
crates.iofutures-io0.3.34futures-test/Cargo.toml
crates.iofutures-util=0.4.0-alpha.0futures-test/Cargo.toml
crates.iofutures-executor=0.4.0-alpha.0futures-test/Cargo.toml
crates.iofutures-sink=0.4.0-alpha.0futures-test/Cargo.toml
crates.iofutures-macro=0.4.0-alpha.0futures-test/Cargo.toml
crates.iopin-project1.0.11futures-test/Cargo.toml
crates.iofutures-core=1.0.0-alpha.0futures-util/Cargo.toml
crates.iofutures-task=0.4.0-alpha.0futures-util/Cargo.toml
crates.iofutures-channel=0.4.0-alpha.0futures-util/Cargo.toml
crates.iofutures-io0.3.34futures-util/Cargo.toml
crates.iofutures-sink=0.4.0-alpha.0futures-util/Cargo.toml
crates.iofutures-macro=0.4.0-alpha.0futures-util/Cargo.toml
crates.ioslab0.4.7futures-util/Cargo.toml
crates.iomemchr2.2futures-util/Cargo.toml
crates.iopin-project-lite0.2.6futures-util/Cargo.toml
crates.iospin0.12.0futures-util/Cargo.toml
crates.ioportable-atomic-util0.2.7futures-util/Cargo.toml
crates.ioportable_atomic_crate1.13.1futures-util/Cargo.toml
crates.iofutures-core=1.0.0-alpha.0futures/Cargo.toml
crates.iofutures-task=0.4.0-alpha.0futures/Cargo.toml
crates.iofutures-channel=0.4.0-alpha.0futures/Cargo.toml
crates.iofutures-executor=0.4.0-alpha.0futures/Cargo.toml
crates.iofutures-io0.3.34futures/Cargo.toml
crates.iofutures-sink=0.4.0-alpha.0futures/Cargo.toml
crates.iofutures-util=0.4.0-alpha.0futures/Cargo.toml
All dependencies 20

Full resolved dependency set from the GitHub dependency graph: 18 direct and 2 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
crates.iofutures-channel0.4.0-alpha.0direct
crates.iofutures-core1.0.0-alpha.0direct
crates.iofutures-executor0.4.0-alpha.0direct
crates.iofutures-io—direct
crates.iofutures-macro0.4.0-alpha.0direct
crates.iofutures-sink0.4.0-alpha.0direct
crates.iofutures-task0.4.0-alpha.0direct
crates.iofutures-util0.4.0-alpha.0direct
crates.iomemchr—direct
crates.iopin-project—direct
crates.iopin-project-lite—direct
crates.ioportable-atomic—direct
crates.ioportable-atomic-util—direct
crates.ioproc-macro2—direct
crates.ioquote—direct
crates.ioslab—direct
crates.iospin—direct
crates.iosyn—direct
crates.ioassert_matches—indirect
crates.iostatic_assertions—indirect
Dependency advisories 17

Installing crates:futures@0.3.34 pulls in 72 packages, direct and transitive: 17 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
tokio0.1.22directhigh21.13.1
crossbeam-utils0.7.2indirecthigh20.8.7
lock_api0.3.4indirectmoderate60.4.2
memoffset0.5.6indirectmoderate20.6.2
net20.2.39indirectunknown1—
tokio-codec0.1.2indirectunknown1—
tokio-current-thread0.1.7indirectunknown1—
tokio-executor0.1.10indirectunknown1—
tokio-fs0.1.7indirectunknown1—
tokio-io0.1.13indirectunknown1—
tokio-reactor0.1.12indirectunknown1—
tokio-sync0.1.8indirectunknown1—
tokio-tcp0.1.4indirectunknown1—
tokio-threadpool0.1.18indirectunknown1—
tokio-timer0.2.13indirectunknown1—
tokio-udp0.1.6indirectunknown1—
tokio-uds0.2.7indirectunknown1—

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — crates.io.