Patch vulnerable frontend dependencies and lockfile#1
Closed
arpitjain099 wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
arpitjain099
force-pushed
the
security/frontend-lockfile-remediation
branch
from
cd1d099 to
61aff8f
Compare
Author
|
Closing this for now. Thanks for the review consideration; may revisit in the future if needed. |
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
vite,react-router-dom,postcss,lovable-tagger)overridesfor vulnerable transitive packages and refreshfrontend/package-lock.jsonnpm audit fix --package-lock-onlyto pull in patched transitive versionsValidation
cd frontend && npm audit(0 vulnerabilities)cd frontend && npm run build