Clear reachable high-severity runtime advisories - #964
Open
fettpl wants to merge 4 commits into
Open
Conversation
fettpl
marked this pull request as ready for review
August 8, 2026 12:49
Contributor
Author
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.
What changed
undici@^7.29.0andminimatch@^10.2.6.proxy-agent@^8.0.2and removed its unused directundicideclaration.brace-expansion@5.0.9,ip-address@10.4.0, and the current SOCKS proxy stack without dependency overrides.Why
The previous lockfile shipped reachable high-severity advisories in the CLI dispatcher, package-pattern, and Bedrock proxy paths. The direct dependency ranges and stale transitive resolutions retained vulnerable
undici,brace-expansion, andip-addressversions; the AI package also declaredundiciwithout using it.Impact
Production installs no longer contain high- or critical-severity advisories reported by npm for these paths. CLI proxy timeouts, package filtering, and Bedrock HTTP/SOCKS proxy behavior remain covered and unchanged.
Checks
npx tsx ../../node_modules/vitest/dist/cli.js --run test/bedrock-endpoint-resolution.test.ts(8 passed)npx tsx ../../node_modules/vitest/dist/cli.js --run test/stdout-cleanliness.test.ts(3 passed)npx tsx ../../node_modules/vitest/dist/cli.js --run test/package-manager.test.ts(96 passed)npx tsx ../../node_modules/vitest/dist/cli.js --run test/model-resolver.test.ts(39 passed)npm run checknpm audit --omit=dev --audit-level=highwith npm 11.19.0 (0 high, 0 critical; moderate-only findings remain outside this issue's gate)npm run audit:prodFixes #931
Note
Clear high-severity runtime advisories in production dependencies
proxy-agentfrom v6 to v8 inpackages/aiand removes the directundicidependency to fix a high-severity advisory in the Bedrock proxy dependency chainminimatchandundiciinpackages/coding-agentto clear high-severity advisories in CLI networking dependenciesaudit:prodnpm script (npm audit --omit=dev --audit-level=high) and a CI step that runs it on every build to catch future high-severity production advisoriesEnvHttpProxyAgentwith unlimited timeouts is installed beforemainrunsMacroscope summarized cf8c38f.