feat: report identity + CVE severity escalation detection - #66
Closed
dmchaledev wants to merge 2 commits into
Closed
feat: report identity + CVE severity escalation detection#66dmchaledev wants to merge 2 commits into
dmchaledev wants to merge 2 commits into
Conversation
added 2 commits
August 7, 2026 12:26
…iff reports Closes #52 - ChangeReport gains from/to SBOMIdentity fields, populated by diff() from each SBOM's parsed identity - Text and markdown reporters render a 'Compared' section stating exactly which two artifacts the report was produced from - JSON output carries the fields naturally (already stringified wholesale) - New test asserts both renderers state the compared artifacts
Closes #46 - New SeverityEscalation type; ChangeReport gains severityEscalations and summary.totalSeverityEscalations - diff() flags a CVE present in both SBOMs whose severity rank increased or whose CVSS score rose (e.g. medium -> critical). De-escalations are not flagged. Such CVEs previously fell into neither newCVEs nor fixedCVEs and were invisible. - Text and markdown reporters render a Severity Escalations section; summary table gains the metric - Tests: escalation detection, CVSS-only rise, de-escalation not flagged
dmchaledev
changed the title
Contributor
Author
|
Superseded — content already merged to main via #67's squash (the branch was based on this PR, so the merge carried both the typescript fix and these features). Verified on main: identity rendering (describeIdentity + ## Compared) and severity escalation detection + tests all present. Closing as redundant. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #52
Problem
diff() read only .components/.vulnerabilities and silently discarded every identity field (name, version, generatedAt, format, specVersion). The report couldn't identify the two artifacts it was produced from — useless for audit output.
Fix
Verification