[Snyk] Fix for 2 vulnerable dependency paths #1604
Merged
Conversation
This file contains 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.
Snyk has identified one or more vulnerable packages in the npm dependencies this project uses.
To fix those, Snyk created this pull request with the necessary changes to address the vulnerabilities.
This pull request includes:
package.jsonscripts and a Snyk policy (.snyk) file, which patch the vulnerabilities that can't be upgraded away.You can read more about Snyk's upgrade and patch logic in Snyk's documentation. Each vulnerability page (see below) includes information about the vulnerable versions, and direct links to the available patches.
This PR includes fixes for the following vulnerabilities:
See the Snyk test report for this project for details.
Some of the vulnerable paths we found do not have a patch nor an upgrade available, and so will remain after merging this PR. You should manually review those issues, and can choose to ignore them by running
snyk wizardin the project's folder.Be sure to check the changes in this PR to ensure they won't cause issues with your application.
Stay secure,
The Snyk team