dependency-audit

Audits Node.js dependency health and internal module coupling across 11 scored dimensions.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill dependency-audit-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-audit
Source: https://github.com/greglas75/zuvo/tree/main/skills/dependency-audit
Command: npx skills add https://github.com/greglas75/zuvo --skill dependency-audit-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Node.js and TypeScript projects accumulate vulnerable, outdated, dead, and license-incompatible dependencies over time, while internal module coupling and circular imports silently degrade architecture. This Skill runs a structured, read-only audit that scores 11 dimensions of dependency health and produces a graded report with a prioritized remediation roadmap. ## Core Features & Use Cases - 11-dimension scoring: Covers supply-chain CVEs, typosquatting and dependency-confusion integrity checks, freshness, dead dependencies, license compliance, bundle weight, circular dependencies, coupling metrics, architecture boundary violations, barrel file health, and change coupling from git history. - Critical gates: Findings such as exploit-grade CVEs, GPL in production, runtime circular dependencies, secrets leaked to client bundles, or confirmed typosquats trigger an automatic FAIL regardless of the numeric score. - Tiered tooling with graceful degradation: Uses npm/pnpm/yarn/bun built-ins first, then npx tools like knip, dependency-cruiser, madge, and license-checker, falling back to grep-based analysis when tools are unavailable. - Use Case: Before a release, run a full audit on a monorepo to get a letter grade, a "Delete These Tomorrow" list of removable dependencies, and a remediation roadmap sorted by effort. ## Quick Start Ask the AI to run a full dependency audit on this project and report the score, critical findings, and unused dependencies.

Frequently Asked Questions about dependency-audit

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

FAQPage Schema
How do I audit npm dependencies for vulnerabilities and dead packages?

Run the dependency audit with no arguments for a full 11-dimension scan, or use --supply-chain for CVE and integrity checks only and --dead for unused dependencies only. It combines npm audit, knip, and lockfile analysis into one scored report.

How to detect circular dependencies in a TypeScript project?

The audit's D6 dimension detects circular dependencies using dependency-cruiser or madge when available, with a grep-based fallback. Runtime cycles causing initialization bugs trigger a critical gate that fails the audit.

Does this dependency audit support pnpm, yarn, and bun?

Yes, it detects the package manager from the lockfile: package-lock.json for npm, pnpm-lock.yaml for pnpm, yarn.lock for Yarn (Classic or Berry), and bun.lockb for Bun. npm-specific features like npm query fall back to lockfile analysis on other managers.

Can I audit Python, Go, or Rust dependencies with this?

No, the audit supports Node.js and TypeScript projects only. Python, Go, Rust, and Java are explicitly listed as unsupported, though Python-specific CodeSift tools run when Python code is detected alongside the Node project.

What happens when audit tools like dependency-cruiser are not installed?

The audit degrades gracefully per dimension rather than failing. Missing tools reduce precision for specific dimensions, such as coupling metrics falling back to grep-based fan-in/fan-out, while the rest of the audit proceeds normally.

Does the dependency audit modify or install packages?

No, the audit is strictly read-only and never runs npm audit fix, installs, or uninstalls anything. Its only write target is the report file saved to the zuvo/audits directory at the project root.