Repository navigation
chore(deps): refresh transitive deps to clear npm audit - #30
Merged
Merged
Conversation
- npm audit reported 5 advisories (2 high, 3 moderate), all reached through the shadcn CLI dependency chain - upstream is now fixed: @modelcontextprotocol/sdk 1.30.0 widened @hono/node-server to "^1.19.9 || ^2.0.5", so the patched 2.x line is finally reachable without an override or a shadcn downgrade - lockfile-only refresh, package.json untouched, no major bumps: @modelcontextprotocol/sdk 1.29.0 -> 1.30.0 @hono/node-server 1.19.15 -> 2.1.0 hono 4.12.32 -> 4.13.0 fast-uri 3.1.4 -> 3.1.5 brace-expansion 5.0.8 -> 5.0.9 - npm audit now reports 0 vulnerabilities; lint and build both pass Tags: #deps #security #lockfile Co-Authored-By: htjulia <htjulia1@gmail.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.
Problem
npm auditonmainreports 5 advisories (2 high, 3 moderate). All of themare reached through a single chain — the
shadcnCLI dependency tree:@hono/node-server<2.0.5 —serve-staticpath traversal (Windows)@modelcontextprotocol/sdk1.25.0–1.29.0hono<4.12.34 — CORS ReDoSfast-uri3.0.0–3.1.4 — host confusionbrace-expansion4.0.0–5.0.8 — DoSPreviously there was no clean remediation: the fix had to land upstream first
(hono → MCP SDK → shadcn), and
npm audit fix --forceonly offered a majorshadcndowngrade.shadcncannot be dropped —src/index.cssimportsshadcn/tailwind.cssas a build-time CSS source.What changed
Upstream is now fixed.
@modelcontextprotocol/sdk@1.30.0widened its range to"@hono/node-server": "^1.19.9 || ^2.0.5", which makes the patched 2.x linereachable. That unblocks a plain lockfile refresh:
package-lock.jsononly —package.jsonis untouchedoverrides, no forced majors, no downgradesVerification
npm audit→ found 0 vulnerabilities (was 5)npm cicleannpm run lint→ no errors (3 pre-existingonly-export-componentswarnings unchanged)npm run build→ passesNotes
Independent of the open dependabot PRs (#28, #29) — this touches only
transitive lockfile entries, so it applies with or without them. Whichever
merges second will need a trivial lockfile rebase.