chore(mcp-server): audit-fix the lockfile to clear 2 open advisories - #446
Merged
Conversation
`mcp-server/` is a separate npm project with its own lockfile, so the root-level audit pass in #442 never touched it. Both of its open Dependabot alerts are runtime-scope transitives of the MCP SDK: - fast-uri 3.1.3 → 3.1.4 — host confusion via a literal backslash authority delimiter (high) - @hono/node-server 1.19.14 → 2.0.12 — serve-static path traversal on Windows via an encoded backslash (moderate) Reaching those required @modelcontextprotocol/sdk 1.29.0 → 1.30.0, which `^1.18.0` already allows, so package.json is unchanged. Lockfile only. `npm audit` in mcp-server/ now reports 0 vulnerabilities. Verified: `npm ci`, `npm run typecheck`, `npm run build`, and a stdio smoke test — initialize succeeds and tools/list still returns all 7 tools on the bumped SDK. Note CI does not cover this directory, so this was checked by hand. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
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
1 participant
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.
Summary
mcp-server/is a separate npm project with its own lockfile, so the root-level audit pass in #442 never reached it. Both of its open Dependabot alerts are runtime-scope transitives of the MCP SDK. Lockfile only — nopackage.jsondiff.What changed
mcp-server/package-lock.json:fast-uri3.1.3 → 3.1.4 — host confusion via a literal backslash authority delimiter (high)@hono/node-server1.19.14 → 2.0.12 —serve-staticpath traversal on Windows via an encoded backslash (moderate)Reaching those required
@modelcontextprotocol/sdk1.29.0 → 1.30.0, which the existing^1.18.0spec already allows.npm auditinsidemcp-server/now reports 0 vulnerabilities.Test plan
CI does not cover this directory — the workflow only installs and builds the root project — so this was verified by hand:
npm ciclean, 0 vulnerabilities.npm run typecheckclean.npm run buildsucceeds.initializereturnswacrm-mcp, andtools/liststill returns all 7 tools on the bumped SDK.Related
Clears 2 of the 3 remaining Dependabot alerts. The third is
sharp— see the note on that PR/issue; it's an optional transitive ofnextand unreachable in this app.