sacp
v11.0.0 ExperimentalCore protocol types and traits for SACP (Symposium's extensions to ACP)
Quick Verdict
- โActively maintained (updated 11d ago)
- โTrusted by 279 crates
- โTeam maintained (2 owners)
- !Heavy dependency tree (22 direct deps)
- โPermissive license (MIT OR Apache-2.0)
Security
Deep Insights
35.5K downloads in the last 30 days (1.2K/day). Volume is roughly flat compared to the previous period.
279 crates depend on sacp. Reasonable ecosystem adoption, though not yet a core dependency.
The primary maintainer publishes 71 crates. This suggests deep Rust expertise and long-term commitment to the ecosystem.
22 direct dependencies. Consider the impact on compile times and supply chain complexity.
Notable dependents include sacp-tokio, sacp-conductor, elizacp, yopo, sacp-rmcp. When high-quality crates choose sacp, 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