ccusage vs minimatch — Trust Score Comparison

Side-by-side trust comparison of ccusage and minimatch. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.

ccusage scores 71.8/100 (B) while minimatch scores 62.8/100 (C) on the Nerq Trust Score. ccusage leads by 9.0 points. ccusage is a coding tool with 10,847 stars, Nerq Verified. minimatch is a uncategorized tool with 0 stars.
71.8
B verified
Categorycoding
Stars10,847
Sourcegithub
Security0
Compliance100
Maintenance0
Documentation0
vs
62.8
C
Categoryuncategorized
Stars0
Sourcenpm_full
Compliance100

Detailed Metric Comparison

Metric ccusage minimatch
Trust Score71.8/10062.8/100
GradeBC
Stars10,8470
Categorycodinguncategorized
Security0N/A
Compliance100100
Maintenance0N/A
Documentation0N/A
EU AI Act RiskN/AN/A
VerifiedYesNo

Verdict

ccusage leads with a trust score of 71.8/100 compared to minimatch's 62.8/100 (a 9.0-point difference). Both agents should be evaluated based on your specific requirements.

Detailed Analysis

Security

Security scores measure dependency vulnerabilities, CVE exposure, and security practices. ccusage scores 0 and minimatch scores N/A on this dimension.

Maintenance & Activity

Activity scores reflect how actively each project is maintained. ccusage: 0, minimatch: N/A.

Documentation

Documentation quality is evaluated based on README, API docs, and example coverage. ccusage: 0, minimatch: N/A.

Community & Adoption

ccusage has 10,847 GitHub stars while minimatch has 0. ccusage has significantly broader community adoption, which typically means more Stack Overflow answers, more third-party tutorials, and faster ecosystem development.

When to Choose Each Tool

Choose ccusage if you need:

  • Higher overall trust score — more reliable for production use
  • Larger community (10,847 vs 0 stars)

Choose minimatch if you need:

  • Consider if it better fits your specific use case

Switching from ccusage to minimatch (or vice versa)

When migrating between ccusage and minimatch, consider these factors:

  1. API Compatibility: ccusage (coding) and minimatch (uncategorized) serve different categories, so migration may require significant refactoring.
  2. Security Review: Run a security audit after migration. Check the ccusage safety report and minimatch safety report for known issues.
  3. Testing: Ensure your test suite covers all integration points before switching in production.
  4. Community Support: ccusage has 10,847 stars and minimatch has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
ccusage Safety Report minimatch Safety Report ccusage Alternatives minimatch Alternatives

Related Pages

Frequently Asked Questions

Which is safer, ccusage or minimatch?
Based on Nerq's independent trust assessment, ccusage has a trust score of 71.8/100 (B) while minimatch scores 62.8/100 (C). The 9.0-point difference suggests ccusage has a stronger trust profile. Trust scores are based on security, compliance, maintenance, documentation, and community adoption.
How do ccusage and minimatch compare on security?
ccusage has a security score of 0/100 and minimatch scores N/A/100. There is a notable difference in their security assessments. ccusage's compliance score is 100/100 (EU risk: N/A), while minimatch's is 100/100 (EU risk: N/A).
Should I use ccusage or minimatch?
The choice depends on your requirements. ccusage (coding, 10,847 stars) and minimatch (uncategorized, 0 stars) serve different use cases. On trust, ccusage scores 71.8/100 and minimatch scores 62.8/100. Review the full KYA reports for each agent before making a decision. Consider factors like integration requirements, documentation quality (0 vs N/A), and maintenance activity (0 vs N/A).

Related Comparisons

Last updated: 2026-04-06 | 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.

We use cookies for analytics and caching. Privacy Policy