Bump semver to ^7.5.3 to resolve security vulnerability#285
Open
Tyharo1 wants to merge 1 commit into
Open
Conversation
Author
|
@rwjblue You appear to be the most active in this code base, is there a specific contributer I should tag to potentially discuss/review this PR? |
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.
The current version of
semverbeing used has a ReDos security vulnerability detected by Snyk. A more recent version ofsemverresolved this issue (v7.5.2 and above). I bumped thesemverversion to its latest to resolve the vulnerability (v7.5.3).For further details on this vulnerability you can view Synks details on it here