chore: tighten stale brace-expansion override - 2026-08-13 - #763
Merged
Conversation
Tighten the brace-expansion override from ^5.0.8 to ^5.0.9. The ^5.0.8 caret still admitted the advisory-vulnerable 5.0.8 (GHSA-rgw5-rvv9-x895 covers <5.0.9), so bumping the floor to ^5.0.9 closes that window. npm audit total unchanged (0 before, 0 after). All gates pass (typecheck, biome check, test, build). The react-scanner>picomatch override is left untouched. Co-Authored-By: Claude Opus 4.8 (1M context) <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
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
Tighten the
brace-expansionentry inpackage.jsonoverrides:Why
The
^5.0.8caret still admitted the advisory-vulnerable5.0.8. GHSA-rgw5-rvv9-x895 covers<5.0.9, so raising the override floor to^5.0.9closes that window and prevents a future resolve from pulling5.0.8back in.Verification
npm ls brace-expansion --allshows every resolution at5.0.9.npm audittotal unchanged: 0 vulnerabilities before → 0 after (did not increase).typecheck,check(biome),test,build, plus husky pre-commit. Biome auto-formatted an unrelated file (src/react-scanner.d.ts) duringcheck; it was reverted so the diff stayspackage.jsononly.react-scanner>picomatchoverride is left untouched.5.0.9, so nopackage-lock.jsonchange was needed.🤖 Generated with Claude Code