build(deps): patch brace-expansion vulnerability - #37
Merged
Conversation
Owner
Author
|
Local proof from e3e877e. The full suite and audit pass. The adversarial 1,500-group input stays under the patched memory cap. |
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
We replaced the vulnerable
brace-expansionversion in the development toolchain with the patched 1.1.18 release.Details
brace-expansionreleases below 1.1.17 to a patched version.react-native-code-push-pluginstays at 1.0.14 because its published tarball doesn't include this development dependency.Testing steps
Run:
pnpm install --frozen-lockfile pnpm audit --audit-level=low pnpm run test --runInBand npm pack --dry-runConfirm the audit reports no known vulnerabilities, the tests pass, and the package tarball builds.