chore: Remediate 12 of 15 Dependabot security alerts (lockfile only) - #250
Merged
Merged
Conversation
Alert-driven lockfile remediation via npm audit fix (rung 1); repo's own prepare-package-lock convention applied. Non-dev upgrades verified available in NpmPrettyMuch.
ernst-dev
changed the title
SpyZzey
approved these changes
Aug 6, 2026
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.
Automated Dependabot security-alert remediation
Alert-driven remediation of this repository's open Dependabot security alerts.
Baseline:
ad62c99c6onmain.Alerts resolved (12 of 15)
fast-uri>= 3.0.0, < 3.1.53.1.5ip-address>= 10.1.1, <= 10.2.010.4.0ip-address>= 10.1.1, <= 10.2.110.4.0ip-address<= 10.3.010.4.0undici>= 7.0.0, < 7.29.07.29.0, 6.28.0undici>= 7.0.0, < 7.29.07.29.0, 6.28.0undici>= 7.0.0, < 7.29.07.29.0, 6.28.0undici>= 7.0.0, < 7.29.07.29.0, 6.28.0undici>= 7.0.0, < 7.29.07.29.0, 6.28.0undici< 6.28.07.29.0, 6.28.0undici< 6.28.07.29.0, 6.28.0undici< 6.28.07.29.0, 6.28.0❌ Alerts NOT resolved by this PR (3) — human decision required
react-router>= 6.0.0, < 7.18.06.30.4react-router>= 6.4.0, < 7.18.06.30.4react-router-dom>= 6.30.2, <= 6.30.46.30.4Why these are not fixed here:
react-router-domhas no patched version at all on the 6.x line (advisory GHSA-jjmj-jmhj-qwj2 lists>= 6.30.2, <= 6.30.4with no first-patched release). The only remediated package in that advisory isreact-router >= 7.13.0.react-routeris only patched at7.18.0— a major v6→v7 upgrade. It is installed here transitively viareact-router-dom@6.30.4, so bumpingreact-routeralone to 7.x would pair a v7 core with a v6 dom package and break at runtime. Pinning it viaoverrideswould produce exactly that broken combination, so it was deliberately not attempted.How this was remediated
npm audit fix --package-lock-only --ignore-scripts(no--forcewas used anywhere in this run).prepare-package-lockconvention (postinstallin@cloudscape-design/build-tools) was applied afterwards, so no@cloudscape-design/*entries are (re-)introduced into the lockfile.dev/optionalflags, unrelated minor bumps). That collateral was deliberately discarded: only the security-relevant entries from npm's computed result were applied on top of the committed lockfile, so this diff contains alert-driven changes only.npm ls --package-lock-only --all: zero new unmet/invalid dependency problems versusmain.Lockfile changes (9)
brace-expansionnode_modules/@typescript-eslint/typescript-estree/node_modules/brace-expansionbrace-expansionnode_modules/brace-expansionbrace-expansionnode_modules/glob/node_modules/brace-expansionbrace-expansionnode_modules/minimatch/node_modules/brace-expansionbrace-expansionnode_modules/readdir-glob/node_modules/brace-expansionfast-urinode_modules/fast-uriip-addressnode_modules/ip-addressundicinode_modules/undiciundicinode_modules/webdriver/node_modules/undiciNPMPM (NpmPrettyMuch) availability — internal build safety
Not applicable — 0 non-dev dependencies changed. Every version bump in this PR is
dev: true, which the NPMPM availability check skips, so there is no internal-build (Brazil) impact and the check should come back green.Does merging clear this repository's alert list?
No — partially. Merging this PR is expected to close 12 of 15 open alerts. 3 will remain open: #151, #150, #149 (
react-router/react-router-dom), which need the v6→v7 migration decision described above.Existing Dependabot-authored PRs were deliberately not touched, reviewed, rebased, or closed by this run.