Repository navigation
chore: resolve Dependabot security alerts - 2026-10-08 - #809
Merged
Merged
Conversation
Bump fast-uri 3.1.7 -> 3.1.8 via npm audit fix. Co-Authored-By: Claude Opus 5 (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
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.
Description of change
UXP-3896 fixed. UXP-4024 stays open, see below.
Bumps
fast-uri3.1.7 to 3.1.8 in the lockfile, closing one of the two auditfindings this repo can currently close.
What is wrong.
npm auditreports 13 findings. One of them,fast-uriunder GHSA-hrr3-gc8f-f4qj, has a patched release available and nothing was
pulling it in. The other 12 all descend from a single root:
bracesat 3.0.3,reached through
@types/shelljstofast-globtomicromatch. That isDependabot alert 85 and UXP-4024.
What this changes. One line in
package-lock.json.npm audit fixappliedit, no range change in
package.json, no new overrides.Why the other 12 are still here. The
bracesadvisoryGHSA-vfj7-8cjw-p6xm, stack exhaustion through deeply nested patterns, has a
patched range of
<=3.0.3, which is to say every published version is affectedand no fix exists upstream yet. An
overridespin has nothing to pin to.npm audit fix --forceclaims it can help, but its plan is four majordowngrades, and it says so itself in the same breath:
Downgrading
react-scanner1.2.0 to 1.1.0 would roll back the scanner thisrepo exists to run, and it would not remove
bracesanyway. I left it.Audit delta. 12 high and 1 moderate before, 11 high after. Nothing regressed.
Pruned overrides. None. The one entry,
react-scanner > picomatch ^2.3.2,is untouched. It is not one of the advisories in play, and I could not tell
from
package.jsonalone whether it is a security pin or a compatibility one.Coordinated PRs. None. This repo has no open Dependabot PRs.
Pull-Request Checklist
mainbranchnpm run lintpasses with this change — N/A, nolintscript.npx biome check ./src/fails, identically onmain, on a formatting error insrc/. Pre-existing, untouched here.npm run testpasses with this change — 3 tests, plustypecheckandbuildpass, and the huskypre-commithook ran cleanFixes #0000— N/A, tracked in Jira, linked aboveHow to review. The diff is one line. The claim worth a second opinion is
that
bracesis genuinely unfixable right now rather than something I gave upon. Check the advisory's patched range yourself if you want to be sure.
🤖 Generated with Claude Code