Crates / futures
Rust crate · real downloads · data Oct 24, 2026
futures downloads, and should you depend on it?
An implementation of futures and streams featuring zero allocations, composability, and iterator-like interfaces. crates.io · docs.rs · repository
Foundational and steady.
futures: 26,505 crates depend on it; downloads don't spike on releases.
How this verdict is decided (4 rules)
- Usage: crates.io reverse dependencies (crates that list it as a dependency): 10,000+ = foundational, 1,000+ = widely used, 100+ = established, under 100 = few direct dependents.
- Direction: the median quiet day in the last 30 days of the window against the first 30, read against the median tracked crate (the whole field moved +36% from late summer to October, so a raw trend says nothing). 10%+ ahead of the field = gaining; 10%+ behind = losing ground; otherwise steady. Steady with no release in 2+ years = quiet for years.
- Release spikes: the median release-window day against the quiet-day baseline: under 1.15x = no spike, 1.15x to 1.3x = small bumps, 1.3x or more = jumps on release days.
- Release recency: days since the newest version that was not yanked, from crates.io publish times.
release window (release day + next day)quiet dayquiet-day median · download the 89 days as CSV
The numbers in one paragraphfutures got 200,567,603 crates.io downloads from Jul 27, 2026 to Oct 23, 2026. 2% of them landed within 2 days of one of its 1 release. On the other 87 quiet days it got a median of 2,405,900 a day, about 16,841,300 a week. Capping release days at that baseline leaves 200,546,279 release-adjusted downloads for the window.
What this means if you're choosing a dependency
- You probably already have it. With 26,505 crates depending on it, it is in most dependency trees. Run
cargo tree -i futuresto see what pulls it into yours before you add it directly. - Actively released. 0.3.34 shipped 2 months ago (Aug 11, 2026).
- Still pre-1.0 (0.3.34). Under Cargo's semver rules a 0.x minor bump may break you, so pin the minor version (
futures = "0.3") and read the changelog on upgrades. - Fit check: license MIT OR Apache-2.0, edition 2018, needs Rust 1.71 or newer (from the latest version's manifest).
- Compare it by the baseline, not the raw count. 2% of its 200,567,603 downloads in the window landed within 2 days of a release; the steady number is 2,405,900 a day.
Alternatives that do a similar job
Crates that share its crates.io category or keywords, most similar first. Each line is the crate's own description, then how it compares on the same data.
Its place in the dependency graph
Built on futures
1 of the 300 crates we track depend on it directly (biggest first).
futures builds on
Tracked crates its latest version (0.3.34) depends on (optional ones marked).
What the chart says
- Weekend quiet days ran at 53% of weekday quiet days (1,352,660 vs 2,569,711). A dip that deep is the signature of work-week CI pipelines and developers building on weekdays.
- Biggest day: 3,392,692 on Oct 22, 2026, a quiet day with no release nearby.
Every number
| All-time downloads | 879,796,181 (rank #114 on crates.io by all-time downloads) |
| Downloads in the window | 200,567,603 (Jul 27, 2026 to Oct 23, 2026, 89 days) |
| Within 2 days of a release | 4,799,001 (2.4%) |
| Quiet-day median (baseline) | 2,405,900 a day; weekdays 2,569,711, weekends 1,352,660 |
| Release-adjusted downloads | 200,546,279 (release-window days capped at the baseline) |
| Baseline rank | #141 of the 300 crates we track |
| Quiet-day trend | +27% raw, -7% against the median tracked crate (+36%) |
| Releases in the window | 1 |
| Versions published, ever | 75 |
| Latest version | 0.3.34, published Aug 11, 2026 (license MIT OR Apache-2.0, edition 2018, MSRV 1.71) |
| First published | Jul 31, 2016 |
| Reverse dependencies | 26,505 |
Releases in the window
Each one opens a 2-day release window on the chart.
| Version | Published | Downloads that version got (lifetime) |
|---|---|---|
| 0.3.34 | Aug 11, 2026 | 48,040,842 |
How we compute this
crates.io counts every download, including CI runners, mirrors and bots that fetch each new version, so raw counts run high (why, in The Manual). We split the last 89 days into release windows (the day a version of futures was published, plus the next day) and quiet days, and use the median quiet day as the baseline: an upper bound on steady use, never a head count. The method and data come from our study of 90 days of crates.io data from 69 crates, featured in This Week in Rust #674; check any crate live with the real-downloads checker.
Badge for your README
Maintainers can show the baseline in a README. It is optional, updates when we refresh the data, and links back here. Preview, then copy:
README, light
README, dark
Publishing a crate of your own? How to publish a Rust crate to crates.io, step by step.
Categories
Sources
- Daily downloads: crates.io API, /crates/futures/downloads (last 90 days, all versions), fetched Oct 24, 2026.
- Versions and publish times: crates.io API, /crates/futures/versions, same fetch.
- Reverse dependencies: crates.io reverse dependencies, same fetch. Dependency edges between tracked crates: each crate's default version, crates.io API.
- Fetched politely (one request every 2 seconds, identified User-Agent) per the crates.io data access policy. Data is crates.io's; the release-window split, baseline and verdict rules are ours, CC BY 4.0.