fix: split CVE reports by scope and correct severity counting#9378
Merged
fix: split CVE reports by scope and correct severity counting#9378
Conversation
Contributor
|
Netlify Draft Deployment |
faa1194 to
0711260
Compare
0711260 to
b83ad59
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Motivation
unknownby fixing the counting logic.Description
scripts/generate-cve-report.mjsto accept--input-prodand--input-allin addition to the legacy--input, and add argument validation for the new modes.collectAdvisoriesandbuildReportSectionhelpers that normalize severities and count them using an explicit=== undefinedcheck so zero/known values are counted correctly..github/workflows/cve-overview.ymlto runpnpm audit --json --productionandpnpm audit --jsonand pass both outputs to the report generator.Testing
pnpm format, which completed successfully.Codex Task