dependency-audit

You can automate dependency version audits across CP repositories to identify mismatches and outdated libraries in Maven, Gradle, and Node projects. This checks version consistency and parent POM alignment across context services.

Parent POM alignment ensures the parent POM chain aligns correctly across context services. Auditing this alignment prevents version inheritance mismatches and maintains build consistency throughout your Continuous Package management system.

Yes, you can perform a pre-upgrade analysis to verify a specific library version across all repositories. This ensures consistent versioning before you apply an upgrade to your Continuous Package environment.

You can scan all context services for outdated dependencies by running an automated audit command across the repository scope. This identifies version inconsistencies and outdated libraries within Maven, Gradle, and Node projects.

Yes, the dependency audit operates within Continuous Package management systems and supports Node repositories. It identifies mismatches and outdated libraries alongside Maven and Gradle environments.

The dependency audit is limited to identifying mismatches, outdated libraries, and POM alignment issues within Maven, Gradle, and Node repositories. It operates strictly within Continuous Package management contexts and does not modify dependencies directly.