Repository navigation
fix(coding-agent): patch vulnerable dependencies - #281
Merged
Merged
Conversation
- Pin Zod 4.6.6 across development and CLI distribution locks, and update sandbox-runtime for compatible declarations. - Pin benchmark filelock 4.2.1 despite the LiteLLM upper bound, with response validation and filesystem-lock regressions. - Address Dependabot alerts 79-84; retain disclosure of the sandbox-only, unpatched node-forge RSA verification advisory.
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.
Summary
Bump Zod 3.25.76 -> 4.6.6 and benchmark filelock from 3.32.7 -> 4.2.1.
Reasoning
The installed MCP SDK built 10,001 validation issues for one oversized completion response before the update; patched Zod rejects it with one size error.
The filelock reproduction deleted an unrelated temporary fixture through a planted SQLite journal before the update; 4.2.1 preserves the fixture.
LiteLLM 1.106.4 still caps filelock below 4, so the benchmark uses an exact uv override with locking compatibility coverage.
Changes
Testing
./test.shpassed after supplying existing generated TUI and telemetry artifacts to the fresh worktree.npm ci --ignore-scripts,npm run check:model-data, andnpm run checkpassed against current main.node --test scripts/dependency-security.test.mjs scripts/distribution-lock-resolution.test.mjs: 8 passed.npm audit --json: zero vulnerabilities.