needs-dependencies

You audit project dependencies by running an orchestrator that detects package managers like npm, Cargo, and Go modules, then checks packages for vulnerabilities, maintenance status, and license violations. It maps dependencies across multi-language projects and reports outcomes for orchestrated minimal updates.

To update outdated npm and Cargo packages safely, the orchestrator reads constraints from docs/constraints.adoc and computes per-dependency updates by type (patch, minor, major). It plans and applies minimal, constraint-aware updates with verification to prevent breaking changes.

Yes, you can detect package managers automatically in a multi-language repository. The tooling identifies package managers such as npm, yarn, bun, pnpm, Cargo, Go modules, and Python tooling, then maps the dependencies found within each ecosystem for analysis.

The best way to check Python tooling dependencies for unmaintained packages is to use an automated audit that analyzes current versus latest versions and maintenance status. This approach identifies unmaintained packages and enables orchestrated, minimal updates to keep software secure.

Dependency update types are computed by analyzing current versus latest versions and categorizing changes as patch, minor, or major updates. The system reads version constraints from docs/constraints.adoc to ensure security patches and vulnerability fixes are applied minimally without violating boundaries.

Automated dependency management is preferred because it detects vulnerable, outdated, and license-violating packages across ecosystems like yarn, pnpm, and Go modules simultaneously. It orchestrates minimal constraint-aware updates with verification, reducing manual error and ensuring continuous compliance.