dependency-audit

Audit Node.js dependency trees for security, health, compliance, and hygiene issues.

3|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill dependency-audit-bensheridanedwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-audit
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/dependency-audit
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill dependency-audit-bensheridanedwards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Node.js projects accumulate dependency risk silently: vulnerable packages, outdated majors, abandoned libraries, missing licenses, unused packages, and lockfile drift. This Skill audits the entire dependency tree against an opinionated baseline and produces structured findings plus an optional implementation plan, without ever installing or modifying anything. ## Core Features & Use Cases - Four-layer audit: Evaluates security (vulnerabilities, lockfile integrity, install scripts), health (outdated, deprecated, abandoned packages), compliance (license coverage, copyleft flagging), and hygiene (unused, misplaced, duplicate dependencies). - Static-first with opt-in network enrichment: Runs read-only by default using package.json and the lockfile; pass --with-network to enrich with the package manager's own audit and outdated registry data. - Structured outputs: Writes findings.md, findings.json (schema 2.0.0), snapshot.md, and metadata.json to .architect-audits/dependency-audit/, then offers to generate a descriptive implementation plan. - Use Case: Before a release, run the audit with --with-network to surface high-severity vulnerabilities, packages more than two majors behind, and GPL-licensed transitive dependencies, then generate a plan listing exact upgrade and removal commands for the team. ## Quick Start Ask the AI to run /dependency-audit on this Node.js project and report the top dependency risks with an implementation plan.

Frequently Asked Questions about dependency-audit

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

FAQPage Schema
How do I audit Node.js dependencies for vulnerabilities and outdated packages?

Run the dependency audit with the --with-network flag, which executes the package manager's own read-only commands like npm audit --json and npm outdated --json. Findings are grouped into security, health, compliance, and hygiene layers with an optional implementation plan.

Does the dependency audit work with pnpm, yarn, and bun?

Yes, it supports npm, pnpm, yarn, and bun by detecting the lockfile or the packageManager field in package.json. Each package manager's read-only audit and outdated commands are used for network enrichment.

Can I run a dependency audit without installing node_modules?

Yes, the audit is tier-based and runs at tier 1 using only package.json and the lockfile when node_modules is absent. Tier-2 checks like license detection degrade to partial with a clear gap message rather than failing.

Does the dependency audit modify package.json or install packages?

No, the audit is fully read-only and never installs, updates, or removes packages. The generated implementation plan is descriptive Markdown listing recommended commands for a human to execute.

Why does the audit report low confidence on unused dependency findings?

Without the Graphify knowledge graph, unused-dependency detection falls back to a regex/AST sweep, which is recorded as low confidence. Running the pre-audit setup to generate graphify-out/graph.json upgrades these findings to high confidence.

What are the limitations of this dependency audit?

It only supports Node.js ecosystems and does not audit Python, Go, Rust, or Ruby dependencies. It also does not perform deep supply-chain analysis such as provenance verification, signature checks, or attestations.