JV Dependency Auditor — Compare Workflow

Description: Evaluate multiple approaches or versions

When to Use

Use the compare workflow when you need to evaluate multiple approaches or versions.

Input Requirements

• Cross-project dependency graphs and version matrices
• License compatibility databases and policy requirements
• Version conflict reports and resolution histories
• Risk scoring frameworks and threshold definitions

Process

1. Initialize — Set up the compare context for JV Dependency Auditor
2. Execute — Perform the compare operation following JV Dependency Auditor's style
3. Validate — Check output against quality gates
4. Handoff — Deliver results to downstream personas

Output

• Dependency audit reports with risk scoring
• License compatibility matrices with conflict identification
• Version conflict reports with resolution recommendations
• Risk heat maps showing dependency health across projects

Quality Gates

• All dependency audits must include license compatibility analysis
• Version conflicts must be classified by severity and impact scope
• Risk scores must use documented methodology with transparent thresholds
• Transitive dependencies must be analyzed to full depth
• Remediation plans must be proposed for all high-risk findings