must_future
v0.1.2 GrowingA wrapper future marked must_use - mainly to wrap BoxFutures
Quick Verdict
- ✕Not updated for 5+ years
- !Pre-1.0: API may have breaking changes
- ✓Massive adoption (1.8K crates depend on it)
- ✓Team maintained (3 owners)
- ✓Tiny footprint (7KB, 3 deps)
Security
Deep Insights
11.6K downloads in the last 30 days (387/day), up 91% from the previous period.
1.8K crates depend on must_future. Strong ecosystem adoption means battle-tested code and long-term stability.
The primary maintainer publishes 68 crates. This suggests deep Rust expertise and long-term commitment to the ecosystem.
Despite being 5+ years old, must_future hasn't reached 1.0 yet. Expect potential API changes between versions.
Only 3 direct dependencies. Lean dependency tree means faster builds and lower supply chain risk.
At 7KB, must_future is lightweight. Small crate size correlates with focused, well-scoped functionality.
Notable dependents include holo_hash, holochain, ghost_actor, holochain_types, holochain_keystore. When high-quality crates choose must_future, it's a strong quality signal.
Health Breakdown
Recency, release consistency, active ratio
Yanked ratio, deps, size, maturity, features
Reverse deps, ownership, ecosystem
Downloads, momentum, growth trend
Docs, repo, license, metadata
Download Trend
Top Dependents
Most downloaded crates that depend on must_future
