deps-audit

Audit npm, Python, Rust, and Go dependencies for CVEs and outdated versions.

Updated May 13, 2026
One-click install
npx skills add https://github.com/usetheodev/theo-ui --skill deps-audit-usetheodev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deps-audit
Source: https://github.com/usetheodev/theo-ui/tree/main/.claude/skills/deps-audit
Command: npx skills add https://github.com/usetheodev/theo-ui --skill deps-audit-usetheodev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit project dependencies for known vulnerabilities (CVEs) and outdated versions across npm, Python, Rust, and Go. Auto-detects manifests; runs osv-scanner + npm audit + npm outdated + pip-audit + cargo audit + govulncheck; cross-references a plan's ## Dependencies section; produces diff-style bump suggestions. NEVER edits manifests. Use after /edge-case-plan, before /plan-confidence — or standalone for periodic audits.

Core Features & Use Cases

  • Auto-detects manifests across npm, Python, Rust, and Go.
  • Executes multi-ecosystem scanners: osv-scanner, npm audit, npm outdated, pip-audit, cargo audit, govulncheck.
  • Cross-references a plan's Dependencies section to validate and suggest changes.
  • Emits read-only diff-style bump recommendations without altering manifests.
  • Suitable for standalone audits or plan-bound reviews during release cycles.

Quick Start

Run the /deps-audit command to generate a read-only report of vulnerable and outdated dependencies.

Frequently Asked Questions about deps-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit project dependencies for known vulnerabilities across npm, Python, Rust, and Go?

Dependency security audit tools detect known CVEs by running osv-scanner, npm audit, pip-audit, cargo audit, and govulncheck against your project manifests, generating read-only diff-style bump recommendations without directly editing your files.

How do I check for outdated npm and Python packages in my repository?

To check for outdated packages, the audit executes npm outdated and pip-audit alongside other ecosystem scanners, analyzing your manifests to produce diff-style bump recommendations for outdated dependencies without modifying the files.

Does this dependency audit tool automatically edit my package manifests?

No, the dependency audit never edits manifests. It performs a read-only scan of your files and outputs diff-style bump recommendations, ensuring your package manifests remain untouched during the vulnerability detection process.

Can I cross-reference a plan's Dependencies section during a security audit?

Yes, the audit supports plan-bound workflows by cross-referencing a plan's Dependencies section to validate and suggest changes. This allows you to align dependency bumps with your project plan during release cycles.

What scanners are used for cross-ecosystem vulnerability detection?

Cross-ecosystem vulnerability detection uses osv-scanner, npm audit, npm outdated, pip-audit, cargo audit, and govulncheck to identify known CVEs and outdated dependencies across npm, Python, Rust, and Go manifests.

When should I run a dependency security audit in my workflow?

Run a dependency security audit after planning and before confidence checks, or as a standalone periodic review. It validates dependencies during release cycles, ensuring your manifests are checked against the latest CVE databases.