analyze-dependencies

To audit project dependencies for vulnerabilities and license compliance, run this skill against your repository to surface direct and transitive dependencies. It analyzes manifests to produce a risk-scored report with actionable recommendations.

Yes, you can scan transitive dependencies across Node.js, Python, Go, Rust, and Java manifests. The skill audits package.json, requirements.txt, go.mod, and other files to inventory all direct and transitive dependencies for comprehensive risk assessment.

The best way to generate a dependency risk report for sprint planning is to run an audit across your codebase manifests. This produces a structured report assessing freshness, vulnerabilities, and maintenance status to prioritize engineering tasks.

Yes, dependency auditing works with multiple ecosystems including Go and Rust. The skill analyzes ecosystem-specific manifests to capture bundle impact, maintenance status, and license compliance, producing a unified risk-scored report.

To assess maintenance status and freshness for codebase dependencies, run an audit to inventory your manifests. The skill evaluates these factors alongside known vulnerabilities and license compliance, producing actionable recommendations for governance.

Auditing transitive dependencies across different language ecosystems requires valid manifest files like package.json or go.mod. The skill relies on these manifests to accurately map direct and transitive dependencies and generate a structured risk-scored report.