Update module security dependencies - #739
Draft
bghgary wants to merge 1 commit into
Draft
Conversation
Move the module's build tooling past the vulnerable tar and flatted dependency paths while preserving the current React Native lock graph. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
[Created by Copilot on behalf of @bghgary]
Context
PR #705 and PR #709 are based on an older lockfile and conflict with current master. This replacement preserves the current React Native dependency graph while removing their vulnerable development-only paths.
Validation
npm audit --package-lock-onlyno longer reportstarorflatted; nine findings outside this update remainDocumentation
N/A; dependency-only change.