dependency-auditor

Scanning dependencies for vulnerabilities and license compliance involves analyzing project files or a dependency inventory to match CVEs and assess licensing risks. This generates structured JSON and human-readable reports with actionable recommendations and risk scoring.

Planning dependency upgrades with phased rollouts requires analyzing current dependency risks and generating a structured upgrade plan. This approach delivers actionable recommendations, risk scoring, and rollback guidance suitable for integrating directly into CI/CD pipelines.

Yes, you can generate consolidated dependency health reports for multiple projects in a CI/CD pipeline. The analysis processes multi-language project files to produce structured JSON and human-readable reports, delivering risk scoring and upgrade plans suitable for automated environments.

Dependency vulnerability scanning works by analyzing either a project directory or a provided dependency inventory. It evaluates security, licensing, and maintenance risks across multi-language ecosystems to output structured JSON and human-readable reports with CVE matching.

CVE matching and risk scoring during a dependency audit work by scanning dependencies against known vulnerabilities and assessing license compliance. It analyzes project files to produce actionable recommendations, structured JSON, and human-readable reports.