dependency-audit

Audit npm, pip, and cargo dependencies for vulnerabilities, outdated packages, and license issues.

20|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/DVNghiem/FlowDeck --skill dependency-audit-dvnghiem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-audit
Source: https://github.com/DVNghiem/FlowDeck/tree/main/src/skills/dependency-audit
Command: npx skills add https://github.com/DVNghiem/FlowDeck --skill dependency-audit-dvnghiem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits npm/pip/cargo dependencies for known vulnerabilities, outdated packages, and license issues. Activate before releases or when CVE alerts are received.

Core Features & Use Cases

  • Security-focused dependency audit across npm, pip, and cargo
  • Detect outdated packages and provide version recommendations
  • License compliance checks with risk indicators
  • Generate consolidated vulnerability reports and remediation guidance

Quick Start

Run the dependency-audit workflow to scan your project's dependencies for vulnerabilities, outdated packages, and license issues.

Frequently Asked Questions about dependency-audit

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

FAQPage Schema
How do I audit dependencies for security vulnerabilities across npm, pip, and cargo?

To audit dependencies for security vulnerabilities across npm, pip, and cargo, this Skill parses your manifest files and runs npm audit, pip-audit, and cargo audit. It generates a unified findings report containing security issues, outdated packages, and license compliance risks.

Can I check dependency license compliance and outdated packages during release preparation?

Yes, you can check dependency license compliance and outdated packages during release preparation. The Skill identifies license issues with risk indicators, detects outdated packages with version recommendations, and outputs consolidated remediation guidance for your release workflow.

What is the best way to handle CVE alerts in a polyglot project?

The best way to handle CVE alerts in a polyglot project is to run a unified dependency audit across your package.json, requirements.txt, and Cargo.toml files. This process scans for known vulnerabilities and generates a consolidated report with actionable remediation guidance.

Does the dependency audit work with both package.json and Cargo.toml manifest files?

Yes, the dependency audit works with package.json, requirements.txt, and Cargo.toml manifest files. It parses these files to identify dependencies, runs the respective package manager audits, and performs license checks to output a unified vulnerability and compliance report.

How do I generate a unified vulnerability report for npm, pip, and cargo?

You generate a unified vulnerability report for npm, pip, and cargo by running the audit workflow. It parses your project manifests, executes the relevant package manager security audits, and consolidates the findings into a single report covering vulnerabilities, outdated packages, and license issues.