Conversation
npm audit fix resolves 26 of 29 advisories (all high and critical ones) within existing semver ranges; only 3 moderate webpack-dev-server advisories remain, below the CI audit gate of --audit-level=high.
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.
What
npm audit fix— package-lock.json only, all updates within existing semver ranges (package.json untouched).Why
The Security Audit CI job (
npm audit --audit-level=high) fails on every PR right now: 29 advisories accumulated since CI last ran on main in January, including 2 critical and 11 high (protobufjs, node-forge, lodash, path-to-regexp, ...). This currently blocks #51 and any other PR.Result
Verified locally: audit gate passes, typecheck clean, webpack CLI build succeeds, flamegraph + parser test suites pass (42/42 Chromium).