Release 2.0.2: fix wrapper verification and local security boundaries - #7
Merged
Conversation
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.
The supported host security wrapper caused a false integrity failure for native
mcp.json. Recognize both MCP formats while rejecting changes to the wrapper's configuration reference, server selector, underlying command, arguments or environment.The accompanying focused security review reproduced and fixes protected-configuration export overwrites (including symlink paths), an implicit sync-log workspace escape, malformed HTTP request crashes, unsafe cleanup after a failed workspace-config save, and known environment credentials appearing in runner result surfaces. Operational adapter/verifier input is preserved. The security review documents the application-level boundaries and redaction limits.
Validation: all component suites and 86 integration tests passed on Node 25; isolated offline package installation and CLI/MCP smoke checks passed; the 449-entry release manifest verified. Focused provider tests passed for origin checks, redirects, request/response limits and cancellation. Dependency audit reported zero vulnerabilities. Required Node 24/25 CI must pass on the merged commit before the v2.0.2 tag. GitHub release only; existing tags stay unchanged.