Repository navigation
fix(deps): zod 4, and the patched transitive releases - #158
Merged
Merged
Conversation
npm audit failed on two high advisories in what users install: zod before 4.6.6 can exhaust memory validating oversized collections, and body-parser before 2.4.0, under the MCP SDK, can be stalled by trailing bytes after a compressed body. zod moves to 4.6.7, which the MCP SDK supports; zod is used only for the MCP tools' argument schemas, which reach clients unchanged. npm audit fix takes the patched body-parser, fast-uri, ip-address and vitest. Co-Authored-By: Claude Opus 5.5 <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.
The scheduled security audit failed on two high advisories in runtime dependencies:
^4.6.7. The MCP SDK supports it (its peer range is^3.25 || ^4.0). SupaForge uses zod only for the MCP tools' argument schemas. I listed the tools over a real MCP connection and confirmed every argument, default, description and check name reaches the client unchanged.npm audit fixtakes the patched body-parser, fast-uri, ip-address and vitest in bothcliandmcp.Left as is: one low esbuild advisory in dev tooling. It affects only esbuild's development server on Windows, which isn't used here.
tsxpins esbuild 0.27, and the gate doesn't fail on it.Tested: the CLI's unit suite and the
mcppackage tests pass, and so do the build and lint.npm auditnow reports nothing formcpand one low advisory forcli.🤖 Generated with Claude Code