What problem does it solve?
Dependency audits prevent production incidents by exposing known vulnerabilities, license incompatibilities, and stale or unused packages before they reach release.
Core Features & Use Cases
- Vulnerability scanning across multiple ecosystems to surface CVEs and prioritize remediation.
- License compliance checks to classify license risk (permissive, weak/strong copyleft, proprietary, unknown) and detect potential conflicts.
- Outdated, bloat, and supply-chain assessments to quantify upgrade urgency, identify unused dependencies, and evaluate maintenance health.
Use case: you are preparing a quarterly release and want a single audit report that highlights critical CVEs, flags GPL/AGPL risks, and ranks major upgrades for planning.
Quick Start
Run the dependency-auditor skill for your repository and request a dependency audit report that includes vulnerabilities, license compliance risk, outdated packages, unused/bloat candidates, and an upgrade priority matrix.