fix CVE-2022-3517 #191
Merged
fix CVE-2022-3517 #191
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
|
If you run I agree that it's time to upgrade the package-lock.json file to v2, but maybe that's a better fit for another PR. |
|
Don't see any problem in just increasing it directly to v2 - otherwise I would have done it manually now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes CVE-2022-3517 by upgrading
globto include the upgrade tominimatchversion greater than3.0.4.Details: https://www.mend.io/vulnerability-database/CVE-2022-3517
Additional notes: I had to run
npm install --forcein order to update the lock file