This repository has been archived by the owner on Dec 6, 2020. It is now read-only.
[Snyk Update] New fixes for 2 vulnerable dependency paths #3
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 project has vulnerabilities that could not be fixed, or were patched when no upgrade was available. Good news, new upgrades or patches have now been published! This pull request fixes vulnerable dependencies you couldn’t previously address.
The PR includes:
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 a Snyk patch:
You can read more about Snyk's upgrade and patch logic in Snyk's documentation.
Note that this pull request only addresses vulnerabilities that previously had no fixes. See the Snyk test report to review and remediate the full list of vulnerable dependencies.
Check the changes in this PR to ensure they won't cause issues with your project.
Stay secure,
The Snyk team