fix(security): bind artifact recovery to file descriptor#16
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.
Summary
Closes the post-merge CodeQL file-system race in artifact export recovery by opening an existing target once, validating descriptor and path identity, reading through the descriptor, and rejecting symlink, replacement, metadata, size, or content drift.
Also aligns all release metadata at v0.6.1 and records the security and release-validation contract.
## Verification
* Complete npm run safe:publish-check passed locally
* 103 test files and 680 tests passed
* Focused authority regression passed 6 of 6
* 53 schemas and 19 evaluator cases passed
* Privacy, brand, package, SBOM, site, CLI, PDF, and DOCX gates passed
## Release boundary
No npm publication. Merge requires the exact PR commit to pass CodeQL, Ubuntu, Windows, native Rust, and dependency review, followed by a zero-open-alert verification.