scc
v3.8.8 StableA collection of high-performance asynchronous/concurrent containers with both asynchronous and synchronous interfaces
Quick Verdict
- โActively maintained (updated 39d ago)
- โStable API (3.x for 5+ years)
- โMassive adoption (2.1K crates depend on it)
- โPermissive license (Apache-2.0)
- !79% of releases were yanked
Security
Deep Insights
7.0M downloads in the last 30 days (233.1K/day), up 11% from the previous period.
2.1K crates depend on scc. Strong ecosystem adoption means battle-tested code and long-term stability.
scc has only 1 owner despite 2.1K 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 254 releases. This level of maturity means you can depend on it without worrying about breaking changes.
79% of releases have been yanked. Check version history before pinning.
Notable dependents include zeromq, dial9-perf-self-profile, metrics-exporter-otel, proto_core, starbase_utils. 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