dependency-auditor

Scan multi-language project dependencies for vulnerabilities, license conflicts, and upgrade paths.

Updated May 21, 2025
One-click install
npx skills add https://github.com/nielslataire/Group-LN --skill dependency-auditor-nielslataire
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-auditor
Source: https://github.com/nielslataire/Group-LN/tree/main/.claude/skills/dependency-auditor
Command: npx skills add https://github.com/nielslataire/Group-LN --skill dependency-auditor-nielslataire

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Modern projects accumulate hundreds of direct and transitive dependencies that introduce security vulnerabilities, license compliance risks, and maintenance debt. Manually auditing package.json, requirements.txt, go.mod, and other manifest files across ecosystems is slow and error-prone, leaving teams exposed to known CVEs and GPL contamination. ## Core Features & Use Cases - Vulnerability Scanning: Parses dependency files across npm, PyPI, Go, Rust, and Ruby ecosystems and matches them against a built-in CVE database with CVSS severity scoring and CI/CD fail-on-high gates. - License Compliance Checking: Classifies dependency licenses into permissive, copyleft, and proprietary risk categories, detects conflicts against the project license, and produces compliance scores. - Upgrade Planning: Generates phased upgrade plans from a dependency inventory with semantic-version risk assessment, security-only filtering, and timeline-based prioritization. - Use Case: A team adds a GitHub Actions step that runs dep_scanner.py with --fail-on-high on every pull request, then feeds the JSON inventory into license_checker.py and upgrade_planner.py to produce a weekly remediation plan. ## Quick Start Ask the assistant to scan your project directory for vulnerable dependencies and generate a license compliance report with an upgrade plan.

Frequently Asked Questions about dependency-auditor

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

FAQPage Schema
How do I scan a project for vulnerable dependencies?▼

Run dep_scanner.py with the project path to parse dependency manifests and match them against the built-in CVE database. Use --format json for machine-readable output or --fail-on-high to make CI pipelines fail when high-severity vulnerabilities are found.

How do I check dependency license compliance in a project?▼

Run license_checker.py against the project directory or pass a dependency inventory JSON with --inventory. It classifies licenses into permissive, weak copyleft, strong copyleft, and proprietary categories, then reports conflicts against your project license with a compliance score.

Which package managers and file formats are supported?▼

The scanner parses package.json, package-lock.json, and yarn.lock for npm; requirements.txt, pyproject.toml, Pipfile.lock, and poetry.lock for Python; go.mod for Go; Cargo.toml and Cargo.lock for Rust; and Gemfile and Gemfile.lock for Ruby.

Does the dependency scanner require external Python packages?▼

No, all three scripts use only the Python standard library and require Python 3.7 or higher. There is nothing to install beyond making the scripts executable with chmod.

Why does the scan report vulnerabilities not listed in public databases?▼

The tool matches dependencies against a built-in vulnerability database covering common CVE patterns, so it will miss newly disclosed or obscure vulnerabilities. You can extend the database by modifying the _load_vulnerability_database method or loading a custom JSON feed.

How do I generate a dependency upgrade plan?▼

Run upgrade_planner.py with a dependency inventory JSON produced by dep_scanner.py. It classifies upgrades by risk level, supports --security-only and --risk-threshold filters, and splits work into three phases across your chosen timeline.