dependency_audit

Audit project dependencies for vulnerabilities, outdated packages, and license issues.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bswrundquist/devtools --skill dependency-audit-bswrundquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency_audit
Source: https://github.com/bswrundquist/devtools/tree/main/src/devtools/templates/claude/user/.claude/skills/dependency-audit
Command: npx skills add https://github.com/bswrundquist/devtools --skill dependency-audit-bswrundquist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to identify and mitigate risks associated with project dependencies, including security vulnerabilities, outdated packages, and licensing conflicts.

Core Features & Use Cases

  • Security Scanning: Detects known vulnerabilities (CVEs) in project dependencies.
  • Freshness Check: Flags packages that are significantly outdated, potentially missing new features or security patches.
  • License Compliance: Identifies potentially problematic licenses (e.g., copyleft) that could conflict with project goals.
  • Unused Dependency Detection: Helps reduce project bloat by identifying declared dependencies that are not actually used.
  • Use Case: A developer can use this Skill to ensure their Python project's dependencies are secure and up-to-date before deployment, preventing potential breaches or compatibility issues.

Quick Start

Run the dependency audit skill to scan the current project's Python dependencies for security vulnerabilities and outdated packages.

Frequently Asked Questions about dependency_audit

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

FAQPage Schema
How do I audit Python dependencies in requirements.txt for security vulnerabilities?

To audit Python dependencies for security vulnerabilities, the skill scans requirements.txt and pyproject.toml files to detect known CVEs and provides actionable remediation recommendations for at-risk packages.

How do I check npm packages for outdated versions and license compliance issues?

Checking npm packages for outdated versions and license issues involves scanning package.json to flag significantly outdated modules and identify potentially problematic licenses, like copyleft, that conflict with project goals.

Can I detect unused dependencies across both pip and npm package managers?

Yes, you can detect unused dependencies across pip and npm environments by scanning project manifests to identify declared components that are not actually used, reducing project bloat.

What is a dependency audit and when do I need to scan my project?

A dependency audit is a process that scans project manifests to identify security vulnerabilities, outdated packages, and license incompatibilities, needed before deployment to prevent potential breaches and compatibility issues.

What is the best way to identify versioning risks and CVEs in project dependencies?

The best way to identify versioning risks and CVEs in project dependencies is to run an audit that scans manifests like requirements.txt and package.json to pinpoint known vulnerabilities and provides actionable recommendations for remediation.