Repository navigation
Patch development source-map-js denial-of-service advisory - #33
Merged
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.
The development test toolchain locks source-map-js 1.2.1, which GitHub flags for high-severity indexed source-map denial of service (Dependabot alert #1). Update only that transitive lockfile entry to patched 1.2.2; runtime dependencies and package versions stay unchanged.
Validation: npm ci and npm run check pass with this lockfile: 348 tests, strict typecheck, build, schema and release metadata. The dependency is reachable through vitest → vite → postcss, not the installed runtime dependency graph. This does not claim to fix the native HTTP/2 incident in #31.