Repository navigation
security: release 1.2.1 - #29
Merged
Merged
Conversation
…nd cap default expansion - Revalidate every resolved long-name path component with the workspace path policy and continue from the canonical path, so 8.3 aliases (e.g. AWS~1) of protected directories and final files are rejected for read and create (PSDK-3-F1). - Share one running budget (10,000 output nodes / 65,536 UTF-8 JSON bytes) across nested default construction so deep defaults throw budget_exceeded instead of exhausting the heap (PSDK-3-F2). - Add regression tests for both findings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016mPGM45PSmJ4yXeBxUF3ox
hkimw
marked this pull request as ready for review
October 15, 2026 03:14
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.
Fix two security issues affecting SDK versions <=1.2.0: protected workspace path reads and creation through Windows short-name aliases, and memory exhaustion during nested default expansion. Prepare version 1.2.1 with updated installation/security guidance and generated version identifiers. Public APIs, declarations, schema contracts and package exports remain compatible.
Validation:
npm run check: 524 runtime tests passed, no skips; public/API/schema checks, TypeScript declarations, example and independent packed consumers passed.The historical candidate benchmark record includes an initial failure and a passing unchanged-candidate confirmation; performance thresholds remain unchanged.
This PR prepares the patch for review. Release publication and npm registry publication are separate actions.