dependency-auditor

To audit dependencies across multiple projects, this Skill scans repositories non-intrusively and logs findings to a centralized Markdown document. It checks for updates, vulnerabilities, licensing concerns, and unused packages, generating reproducible reports without modifying your code.

A dependency audit identifies risky or outdated packages in your codebase and logs them to a structured Markdown report. The generated document includes dedicated sections for Summary, Updates, Vulnerabilities, Licenses, and Unused dependencies.

Yes, you can trigger this dependency health check in a CI pipeline without modifying code. The Skill performs non-intrusive scans to surface risky upgrades and licensing conflicts, outputting results to a structured audit document for review.

Yes, the dependency audit supports multiple projects and languages. It applies reproducible reporting to identify unused dependencies, vulnerabilities, and licensing concerns across diverse codebases.

Dependency audit findings are documented in a structured Markdown report under .documents/_ops/DEPENDENCY_AUDIT.md. The report includes clear citations for all identified updates, vulnerabilities, licenses, and unused dependencies.

The best way to detect unused dependencies and licensing conflicts is using an automated audit tool that scans repositories non-intrusively. It generates a structured Markdown report with reproducible findings and clear citations for review.