Score8.1
Popularity9.0
Riskconditional
TierSilver
Score breakdown
Usefulness8.0
Novelty8.0
Momentum4.0
Maturity6.1
Open-source/build8.4
Evidence7.2
Workflow potential8.9
Setup ease6.4
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that are starting to let agents add or modify capabilities in codebases: run it on a staging repository first and see whether its static checks catch risky tool-surface changes without flooding reviewers with noise.
Who should use it
Who should skip it
Skip if the source link, docs, or setup requirements do not match your workflow.
Risk explanation
Because it can become part of your merge gate for agent-generated capability changes, validate its policies on a staging repo first so false positives or blind spots do not quietly shape production review decisions..