Skip to content

Commit 01ce5a1

Browse files
authored
Merge pull request #134 from karthikcsq/fix/audit-129
Clear all production and dev npm audit findings (#129)
2 parents a95bf30 + ec27617 commit 01ce5a1

4 files changed

Lines changed: 206 additions & 161 deletions

File tree

docs/decisions/2026-08-16-mcp-sdk-v2-compatibility-spike.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,3 +136,18 @@ deliberately the exception, preserved to detect the upstream fix.
136136
This phase does not replace FastMCP, modify `dist/index.js`, remove session
137137
routes, migrate error imports, or create production HTTP/stdio handlers. Those
138138
changes remain Phase 2 and must use the observed contracts above.
139+
140+
## Amendment, 2026-08-31: Hono floor raised to `^4.13.5`
141+
142+
The manifest request for `hono` moved from `^4.11.4` to `^4.13.5` while clearing the
143+
production audit findings in #129. Every hono release through 4.12.33 carries published
144+
advisories, so a manifest floor of `^4.11.4` permitted a resolution that `npm audit` flags,
145+
even though the lockfile in this repository resolved a patched build.
146+
147+
`@modelcontextprotocol/node@2.0.0` still declares `peerDependencies.hono` as `^4.11.4`.
148+
`^4.13.5` is a strict subset of that range, so this tightens the floor without changing which
149+
SDK version is compatible. `tests/mcpSdkV2Compatibility.test.js` asserts both the new floor and
150+
the SDK's declared peer range, so a future SDK release that narrows its peer range will fail
151+
loudly rather than resolve to something unintended.
152+
153+
The table above is the record of the original spike and is left as it was on 2026-08-16.

0 commit comments

Comments
 (0)