awesome-claude-code-plugins vs ccmanager — Trust Score Comparison
Side-by-side trust comparison of awesome-claude-code-plugins and ccmanager. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | awesome-claude-code-plugins | ccmanager |
|---|---|---|
| Trust Score | 0.0/100 | 80.1/100 |
| Grade | D | A |
| Stars | 487 | 831 |
| Category | coding | coding |
| Security | N/A | 1 |
| Compliance | 100 | 87 |
| Maintenance | 0 | 1 |
| Documentation | 0 | 1 |
| EU AI Act Risk | N/A | minimal |
| Verified | No | Yes |
Verdict
ccmanager leads with a trust score of 80.1/100 compared to awesome-claude-code-plugins's 0.0/100 (a 80.1-point difference). ccmanager scores higher on maintenance (1 vs 0). Both agents should be evaluated based on your specific requirements.
Detailed Analysis
Security
Security scores measure dependency vulnerabilities, CVE exposure, and security practices. awesome-claude-code-plugins scores N/A and ccmanager scores 1 on this dimension.
Maintenance & Activity
ccmanager demonstrates stronger maintenance activity (1/100 vs 0/100). This metric captures commit frequency, issue response times, and release cadence. Actively maintained tools receive faster security patches and are less likely to accumulate technical debt.
Documentation
ccmanager has better documentation (1/100 vs 0/100). Good documentation reduces onboarding time and helps teams adopt the tool safely. This score evaluates README completeness, API documentation, code examples, and tutorial availability.
Community & Adoption
awesome-claude-code-plugins has 487 GitHub stars while ccmanager has 831. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.
When to Choose Each Tool
Choose awesome-claude-code-plugins if you need:
- Consider if it better fits your specific use case
Choose ccmanager if you need:
- Higher overall trust score — more reliable for production use
- Stronger security profile with fewer known vulnerabilities
- More actively maintained with faster release cadence
- Larger community (831 vs 487 stars)
- Better documentation for faster onboarding
Switching from awesome-claude-code-plugins to ccmanager (or vice versa)
When migrating between awesome-claude-code-plugins and ccmanager, consider these factors:
- API Compatibility: awesome-claude-code-plugins (coding) and ccmanager (coding) share similar interfaces since they are in the same category.
- Security Review: Run a security audit after migration. Check the awesome-claude-code-plugins safety report and ccmanager safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: awesome-claude-code-plugins has 487 stars and ccmanager has 831. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-11-12 | Data refreshed weekly
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.