Repository navigation
test: cover prototype poisoning through Expo config merges - #57
Merged
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
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
Add a regression for prototype poisoning through Expo's config merge, where the patched deepmerge dependency is used.
Details
__proto__key, merges a safe setting through Expo, and checks the returned object has no poisoned prototype.69f72b6abf7b7fe37cedc2d3ff1cc8208ae96789. Every tracked file was compared byte for byte with the published Git tree. Author and committer are Gabriel Taveira gabrielstaveira@gmail.com.Testing steps
Run with Node 24 and pnpm 11.17.0:
pnpm install --frozen-lockfile pnpm run lint pnpm run format pnpm run typecheck pnpm run test pnpm run build pnpm run changelog:check pnpm run security:check npm pack --dry-runThe Expo merge should reject prototype poisoning while preserving the safe config values. The audit still lists three advisory exceptions covered by the existing local patches and regression checks.