AI Developer Tools
deptrust
A CLI tool that checks package versions for known vulnerabilities across npm, PyPI, and many other ecosystems, designed for AI agents to avoid using outdated packages.
deptrust
What is deptrust?
deptrust is a CLI tool that checks package versions for known vulnerabilities across multiple package ecosystems. It runs locally as a CLI and as an MCP server, calling public registries and OSV APIs directly without a hosted service.
deptrust vs Similar AI Tools
| Pricing Model | Free | Free | Custom Pricing | Free, Paid |
| Free Credits | ||||
| Key Features |
|
|
|
|
| Pros |
|
|
|
|
| Cons |
|
|
|
|
| Best For |
|
|
|
|
How to use deptrust?
- 1Install with npx @clidey/deptrust install. Run checks like 'deptrust check npm lodash 4.17.20' or 'deptrust check pypi requests latest'. For AI agent integration, configure MCP with 'deptrust mcp'. Use JSON output with '--json' flag.
deptrust Key Features
- Checks packages across 15+ ecosystems including npm, PyPI, Cargo, Go, RubyGems, NuGet, Maven, and more
- Reports known vulnerabilities with severity, recommendation, and risk score
- Suggests safe versions by checking provider-reported fixes and version history
- Compares two versions to show risk improvement
- Integrates as MCP server for AI agents (Codex, Claude Code)
- Runs entirely locally with no external service dependency
- Outputs JSON with advisory coverage details
deptrust Use Cases
- AI agents checking package versions before recommending updates
- Developers auditing project dependencies for vulnerabilities
- CI/CD pipelines enforcing package version policies
- Security teams reviewing dependency risk scores
deptrust Pricing & Free Credits
deptrust currently operates on a Free model.
This tool is completely free to use
deptrust Pros & Cons
Pros
- Supports a wide range of package ecosystems
- Runs locally with fast parallel queries to public APIs
- Integrates seamlessly with AI agents via MCP protocol
- Provides clear recommendations (allow/block/review) and risk scores
- Open source and no need for account or API keys
Cons
- Only checks known vulnerabilities, does not perform code analysis
- Requires MCP setup for AI agent integration, which may be complex
- Depends on OSV and GitHub Advisory Database coverage per ecosystem
- Some ecosystems have partial advisory coverage (e.g., CocoaPods, Hackage)
What is deptrust best for?
- AI developers building agentic workflows
- Developers who want to prevent vulnerable dependency picks
- DevSecOps teams needing a lightweight vulnerability checker
- Anyone using package managers in automated environments