Update vulnerable JavaScript dependencies - #257
Merged
Conversation
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.
Summary
brace-expansionranges to1.1.18and2.1.4js-yamlrange to3.15.1package-lock.jsonwith the resolved patched versionsWhy
The JavaScript test toolchain resolved vulnerable transitive versions even though the direct Jest dependencies were current. Package overrides keep the existing toolchain while forcing patched versions.
Impact
This changes development and test dependencies only. Runtime .NET behavior is unaffected.
Validation
npm cinpm run test:js(190 passed)npm audit --audit-level=high --json(0 vulnerabilities)