Repository navigation
fix(deps): bump , 3.1.7, 5.0.9 to patched releases (CVE sweep 2026-09-30) - #262
Merged
Merged
Conversation
… sweep 2026-09-30) Lockfile-only, hand-applied: each vulnerable record moves to the fixed patch of its own major (brace-expansion 1.1.21 / 5.0.12, fast-uri 3.1.8 / 4.1.5) with version, resolved and integrity taken from the registry. Dependencies, engines and license of the target versions are unchanged, so no other record moves; rewriting the lock with npm 10 would strip unrelated libc arrays written by npm 11. Advisories: GHSA-q2hr-2g5m-vwhr, GHSA-qhr7-859c-m2p7, GHSA-6j4f-fj2g-mc7p (brace-expansion), GHSA-hrr3-gc8f-f4qj (fast-uri). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Lockfile-only CVE fix.
node_modules/brace-expansionnode_modules/fast-uriAdvisories:
The brace-expansion/fast-uri records were hand-applied: version, resolved and integrity taken from the registry (
npm view <pkg>@<ver> dist.tarball dist.integrity); dependencies, engines and license of the target versions are unchanged, so no other record moves. Letting npm 10 rewrite the lock would strip unrelatedlibcarrays written by npm 11.Verified on a clean extract under the CI Node:
npm ci --ignore-scriptsexit 0,npm auditno longer lists these packages and no new advisory versus the base branch. Independently reviewed (registry values for every changed record, clean-extract installs).🤖 Generated with Claude Code