Audit this project's dependencies. If $ARGUMENTS are provided, scope the audit accordingly (e.g., a specific package, dimension, or ecosystem).
1. Detect ecosystem
Identify which package managers are present and their lock files.
| Manifest |
Ecosystem |
Audit Tool |
Outdated Tool |
| package.json |
Node.js |
npm audit |
npm outdated |
| pyproject.toml / requirements.txt |
Python |
pip-audit |
pip list -o |
| go.mod |
Go |
govulncheck |
go list -m -u |
| Cargo.toml |
Rust |
cargo audit |
cargo outdated |
| Gemfile |
Ruby |
bundle-audit |
bundle outdated |
| composer.json |
PHP |
composer audit |
composer outdated |
2. Three-dimension audit
Run each check using the ecosystem's native tooling. If any dimension's tool isn't installed, note it in the report and skip that dimension rather than failing.
- Vulnerabilities — run the native audit tool (see table above); classify findings by severity (critical / high / medium / low)
- Outdated — check for outdated dependencies; flag major version bumps separately from minor/patch; note packages more than 6 months behind latest (get release dates from the registry, e.g.
npm view <pkg> time, PyPI's https://pypi.org/pypi/<pkg>/json, gem info <pkg>; if dates aren't obtainable, say so instead of guessing)
- Licenses — identify dependency licenses using the ecosystem's license tool; determine the project's own license from its
LICENSE/LICENSE.md file, or the manifest's license field (package.json, pyproject.toml, etc.) if no LICENSE file exists; flag licenses that conflict with the project's own — strong copyleft (GPL, AGPL) in a permissive or proprietary project is the main concern, whereas the same license in a matching copyleft project is fine; treat weak copyleft (LGPL, MPL, EPL) as conditional (usually OK for an unmodified, dynamically linked dependency); always flag unknown/unlicensed dependencies
| Ecosystem |
License Tool |
| Node.js |
license-checker |
| Python |
pip-licenses |
| Go |
go-licenses |
| Rust |
cargo-license |
| Ruby |
license_finder |
| PHP |
composer licenses |
If no manifest is found, report that no ecosystem was detected; if multiple are found, run each and merge into one report.
Multiple manifests, same ecosystem (npm/yarn workspaces, Go multi-module repos, monorepo packages): glob for nested manifests (e.g. **/package.json, **/go.mod, excluding node_modules/vendor) and aggregate results per workspace/module rather than auditing only the repo root.
3. Output format
Produce a structured report with:
- Summary — ecosystem, total deps, issue counts by severity
- Vulnerabilities table — package, severity, CVE, fix version
- Outdated table — package, current version, latest version, bump type, months behind latest
- License issues — package, license, concern
- Prioritized remediation steps — ordered by severity then effort
Example:
Summary — Node.js, 142 deps, 2 critical, 5 high, 1 license issue
| Package |
Severity |
CVE |
Fix Version |
| lodash |
critical |
CVE-2021-23337 |
4.17.21 |
| minimist |
high |
CVE-2020-7598 |
1.2.6 |
| Package |
Current |
Latest |
Bump |
| express |
4.17.1 |
4.19.2 |
minor |
License issues — left-pad@GPL-3.0 conflicts with project's MIT license
Do not use when
- Auditing code quality rather than dependencies — use
code-audit
1---2name: deps-audit3description: Audits project dependencies for vulnerabilities, outdated packages, and license issues. Use when checking dependency health, running security audits, or reviewing package versions. Covers native audit tools, version freshness, and license compliance.4---56Audit this project's dependencies. If $ARGUMENTS are provided, scope the audit accordingly (e.g., a specific package, dimension, or ecosystem).78## 1. Detect ecosystem910Identify which package managers are present and their lock files.1112| Manifest | Ecosystem | Audit Tool | Outdated Tool |13| --------------------------------- | --------- | ---------------- | ------------------- |14| package.json | Node.js | `npm audit` | `npm outdated` |15| pyproject.toml / requirements.txt | Python | `pip-audit` | `pip list -o` |16| go.mod | Go | `govulncheck` | `go list -m -u` |17| Cargo.toml | Rust | `cargo audit` | `cargo outdated` |18| Gemfile | Ruby | `bundle-audit` | `bundle outdated` |19| composer.json | PHP | `composer audit` | `composer outdated` |2021## 2. Three-dimension audit2223Run each check using the ecosystem's native tooling. If any dimension's tool isn't installed, note it in the report and skip that dimension rather than failing.2425- **Vulnerabilities** — run the native audit tool (see table above); classify findings by severity (critical / high / medium / low)26- **Outdated** — check for outdated dependencies; flag major version bumps separately from minor/patch; note packages more than 6 months behind latest (get release dates from the registry, e.g. `npm view <pkg> time`, PyPI's `https://pypi.org/pypi/<pkg>/json`, `gem info <pkg>`; if dates aren't obtainable, say so instead of guessing)27- **Licenses** — identify dependency licenses using the ecosystem's license tool; determine the project's own license from its `LICENSE`/`LICENSE.md` file, or the manifest's `license` field (`package.json`, `pyproject.toml`, etc.) if no LICENSE file exists; flag licenses that conflict with the project's own — strong copyleft (GPL, AGPL) in a permissive or proprietary project is the main concern, whereas the same license in a matching copyleft project is fine; treat weak copyleft (LGPL, MPL, EPL) as conditional (usually OK for an unmodified, dynamically linked dependency); always flag unknown/unlicensed dependencies2829| Ecosystem | License Tool |30| --------- | ------------------- |31| Node.js | `license-checker` |32| Python | `pip-licenses` |33| Go | `go-licenses` |34| Rust | `cargo-license` |35| Ruby | `license_finder` |36| PHP | `composer licenses` |3738If no manifest is found, report that no ecosystem was detected; if multiple are found, run each and merge into one report.3940**Multiple manifests, same ecosystem** (npm/yarn workspaces, Go multi-module repos, monorepo packages): glob for nested manifests (e.g. `**/package.json`, `**/go.mod`, excluding `node_modules`/`vendor`) and aggregate results per workspace/module rather than auditing only the repo root.4142## 3. Output format4344Produce a structured report with:4546- **Summary** — ecosystem, total deps, issue counts by severity47- **Vulnerabilities table** — package, severity, CVE, fix version48- **Outdated table** — package, current version, latest version, bump type, months behind latest49- **License issues** — package, license, concern50- **Prioritized remediation steps** — ordered by severity then effort5152Example:5354> **Summary** — Node.js, 142 deps, 2 critical, 5 high, 1 license issue55>56> | Package | Severity | CVE | Fix Version |57> | -------- | -------- | -------------- | ----------- |58> | lodash | critical | CVE-2021-23337 | 4.17.21 |59> | minimist | high | CVE-2020-7598 | 1.2.6 |60>61> | Package | Current | Latest | Bump |62> | ------- | ------- | ------ | ----- |63> | express | 4.17.1 | 4.19.2 | minor |64>65> **License issues** — `left-pad@GPL-3.0` conflicts with project's MIT license6667## Do not use when6869- Auditing code quality rather than dependencies — use `code-audit`