Clear all open security advisories - #57
Merged
Merged
Conversation
GitHub reported 15 open Dependabot alerts against the lockfiles that landed in #46, six of them high. Dependabot opened eight PRs for them; this fixes the underlying alerts in one change instead. react-router 7 -> 8 in spa/react is a genuine major, and the only route to the fix: react-router-dom is capped at 7.18.2, so the patched version only exists in the `react-router` package. Four imports move (BrowserRouter, Routes, Route, useNavigate). This was the last outstanding major upgrade in the repo. Everything else was transitive. Most cleared with `npm audit fix`, which is non-breaking: path-to-regexp 8.3.0 -> 8.4.2 HIGH, ReDoS qs 6.15.0 -> 6.15.3 MEDIUM, DoS body-parser 2.2.2 -> 2.3.0 LOW Three could not, because npm's own fix proposes a multi-major downgrade of the direct dependency -- next@9.3.3 (from 16), @sveltejs/kit@0.0.30 (from 2.70), @angular/cli@21 (from 22). Those use npm `overrides` to pin the patched transitive instead: postcss ^8.5.24 HIGH, XSS + path traversal sharp ^0.35.3 HIGH, libvips CVEs cookie ^0.7.2 LOW @hono/node-server ^2.0.12 MEDIUM That last one also resolves the advisory left open in #46, where the only offered fix was downgrading the Angular CLI. Supersedes Dependabot #41 and #48-55; every version those PRs asked for is now met or exceeded. The two rand PRs no longer apply at all -- jsonwebtoken's rust_crypto backend pulls 0.8.7 and 0.10.2, not the 0.9.x line they target. Verified: 27/27 build and smoke; web, mcp, a2a, native and claims suites = 69 passed, 0 failures. npm audit clean in all 11 directories, pip-audit clean in all 10. Co-Authored-By: Claude <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.
GitHub reported 15 open Dependabot alerts against the lockfiles that landed in #46 — 6 high. Dependabot opened 8 PRs for them; this fixes the underlying alerts in one change instead.
The one real major
react-router7 → 8 inspa/react, and it's the only route to the fix:react-router-domis capped at 7.18.2, so the patched version only exists in thereact-routerpackage. Four imports move (BrowserRouter,Routes,Route,useNavigate).This was the last outstanding major upgrade in the repo — everything else is now on its current major.
Non-breaking transitive fixes
path-to-regexpqsbody-parserThree needed
overridesFor these,
npm audit fix --forceproposes a multi-major downgrade of the direct dependency — worse than the vulnerability:So they pin the patched transitive via npm
overridesinstead, leaving the direct dependency alone:postcss ^8.5.24sharp ^0.35.3cookie ^0.7.2@hono/node-server ^2.0.12That last one also resolves the advisory I deliberately left open in #46, where the only offered fix was downgrading the Angular CLI.
Supersedes the Dependabot PRs
Closes #41 and #48–#55. Every version they ask for is now met or exceeded:
path-to-regexpqsbody-parserquinn-protoserde_withrustls-webpki#49 and #52 (
rand→ 0.9.5) no longer apply:jsonwebtoken'srust_cryptobackend pulls 0.8.7 and 0.10.2, not the 0.9.x line they target.Verification
27/27 build and smoke · web, mcp, a2a, native, claims = 69 passed, 0 failures ·
npm auditclean in all 11 directories ·pip-auditclean in all 10 ·cargo build --lockedclean🤖 Generated with Claude Code