Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI coding-agent authors, security engineers, and platform teams who need a dependency-vulnerability gate that runs locally and integrates with the same MCP, SKILL.md, and hook surfaces their agents already use, so old vulnerable packages get caught at install time across npm, PyPI, crates.io, Go modules, and a dozen other ecosystems without sending a single byte to a hosted service
Who should use it
Who should skip it
Consider clidey/deptrust lower priority if you already have a working solution in this category.
About this signal
clidey/deptrust is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-09 and last updated on 2026-07-09. The current verdict is 'try now' with a Silver tier and easy setup difficulty. The standout signals for clidey/deptrust are momentum (9.0) and setup ease (8.8), while maturity (5.7) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned clidey/deptrust a composite score of 7.8 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'none' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
No inherent user-impacting risk is flagged from the captured evidence.