chore(security): bundle npm transitive fixes for root package-lock.json - #24
Open
benfrank241 wants to merge 1 commit into
Open
chore(security): bundle npm transitive fixes for root package-lock.json#24benfrank241 wants to merge 1 commit into
benfrank241 wants to merge 1 commit into
Conversation
Raise the fast-uri override to ^3.1.6 (resolves 3.1.7) and add a qs override at ^6.16.0 (resolves 6.16.0), clearing 5 Dependabot alerts. Both packages are transitive-only, and every declaring parent accepts the patched range (fast-uri: ajv ^3.0.1; qs: body-parser ^6.15.2, express ^6.14.0), so plain global overrides are correct here. Verified locally with the exact CI steps: npm ci, npm run build, npm run lint -- all green; npm audit reports 0 vulnerabilities. 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
2 participants
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.
Daily security sweep. Recreates the Dependabot fixes for the root
package-lock.jsonon a human-authored branch so the change actually gets CI (Dependabot's own branches don't receive CI secrets, so its PRs fail with no signal).Alerts closed by this PR
>= 3.0.0, < 3.1.6>= 3.0.0, < 3.1.6>= 3.1.2, < 3.1.6>= 3.1.3, < 3.1.6>= 6.14.2, <= 6.15.3Changes
Both packages are transitive only — neither is a direct dependency — so both are fixed via
overrides:fast-uri: existing override raised3.1.5→^3.1.6(resolves to 3.1.7). The3.1.5pin came from chore(security): bundle 21 Dependabot alerts for root package-lock.json #23 and is itself now in the vulnerable range.qs: new override^6.16.0(resolves to 6.16.0).Global (unscoped) overrides are correct here — every declaring parent accepts the patched range, so nothing innocent gets rewritten:
fast-uri←ajv(x2, under@modelcontextprotocol/sdkandajv-formats), both^3.0.1qs←body-parser^6.15.2,express^6.14.0Caret rather than
>=so npm cannot jump a major past what those parents allow.Lockfile churn is 5 entries: the two targets plus
side-channel1.1.0→1.1.1,side-channel-list1.0.0→1.0.1 andes-object-atoms1.1.1→1.1.2, all patch-level and all insideqs's own subtree. No packages added or removed.Verification
Ran the exact steps from
.github/workflows/ci.ymllocally, all green:npm cinpm run buildnpm run lintnpm auditreports 0 vulnerabilities. There is notestscript in this package, so that step is skipped (CI doesn't run one either).No majors, no forced resolves (
--force/--legacy-peer-depswere not used), and no unrelated changes bundled in.