This repository has been archived by the owner on Jun 6, 2022. It is now read-only.
[Snyk] Fix for 30 vulnerable dependency paths #2
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.
This pull request fixes one or more vulnerable packages in the npm dependencies of this project. See the Snyk test report for this project for details.
The PR includes:
package.json
to upgrade the vulnerable dependencies to a fixed version.package.json
scripts and a Snyk policy (.snyk
) file, which patch the vulnerabilities that can't be upgraded away and ignore vulnerabilities with no fixes.Vulnerabilities that will be fixed
With an upgrade:
With a Snyk patch:
Note that some vulnerabilities couldn’t be fully fixed and weren’t explicitly ignored, and so will still fail the Snyk test report.
You can read more about Snyk's upgrade and patch logic in Snyk's documentation.
Check the changes in this PR to ensure they won't cause issues with your project.
Stay secure,
The Snyk team