Fix data-root path boundary checks#11
Open
bittoby wants to merge 1 commit into
Open
Conversation
bittoby
force-pushed
the
fix/path-boundary-guards
branch
from
ca79db3 to
4b40ef3
Compare
bittoby
force-pushed
the
fix/path-boundary-guards
branch
from
44a80d2 to
d8a81f9
Compare
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
Fixes data-root path boundary checks so sibling directories with the same string prefix as
PRODUCT_MCP_DATA_DIRare not treated as inside the data root.What Changed
isPathInsideRoot()helper usingpath.relative().startsWith(REPO_ROOT/DATA_DIR)checks in source, extraction, audit, and schema-generation path resolution.Validation
npm testnpm run buildFixes #10