Skip to content

fix: preserve accepted conflicting version evidence - #9

Merged
CompleteDotTech merged 1 commit into
mainfrom
fix/audit-7-conflict-evidence
Oct 26, 2026
Merged

CompleteDotTech merged 1 commit into
mainfrom
fix/audit-7-conflict-evidence

Conversation

@CompleteDotTech

Copy link
Copy Markdown
Contributor

Conflicting accepted Next.js versions previously collapsed to identical reports: 16.4.0/16.4.1 and 16.3.0/16.4.2 lost their exact candidates. Retain bounded validated observed_version on each evidence source, project it in HTML and CSV/JSON, and align schema, methodology, examples and generated standalone/checksums. Conflicts remain unknown with exploitability=not_tested; malformed, qualified and URL-shaped raw input stays excluded.

Validation: 91 offline synthetic unit tests pass (4 Windows platform skips), build consistency check, actual CLI help, synthetic HTML example generation and git diff --check pass. Regression cases cover distinct conflicting pairs, per-source association across all formats, mixed invalid/valid evidence and schema rejection of unsafe values. No target scans or runtime execution. Hosted CI and actual final-head Copilot review remain merge gates.

Fixes #7

@CompleteDotTech
CompleteDotTech merged commit 7df821c into main Oct 26, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[P2] Preserve accepted conflicting versions in exported evidence

1 participant