scc
v3.8.4 StableA collection of high-performance asynchronous/concurrent containers with both asynchronous and synchronous interfaces
Quick Verdict
- ✓Actively maintained (updated 7d ago)
- ✓Stable API (3.x for 5+ years)
- ✓Massive adoption (1.6K crates depend on it)
- ✓Permissive license (Apache-2.0)
- !80% of releases were yanked
Security
Deep Insights
5.4M downloads in the last 30 days (179.3K/day). Volume is roughly flat compared to the previous period.
1.6K crates depend on scc. Strong ecosystem adoption means battle-tested code and long-term stability.
scc has only 1 owner despite 1.6K dependents. This is a bus-factor concern — consider the implications for long-term support.
The API has been stable (1.x) for over 5 years with 250 releases. This level of maturity means you can depend on it without worrying about breaking changes.
80% of releases have been yanked. Check version history before pinning.
Notable dependents include syd, zeromq, proto_core, starbase_utils, warpgate. When high-quality crates choose scc, 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