This repository has been archived by the owner on Feb 8, 2018. It is now read-only.
[Snyk Alert] Fix for 2 vulnerable dependency paths #1
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 following newly disclosed vulnerabilities impact one or more of the npm packages this project uses:
As these vulnerabilities are now publicly known, attackers can try to use them against your application, making fixing them a matter of urgency.
To help expedite the fix, Snyk created this pull request with the necessary changes to address the vulnerabilities.
This pull request includes:
package.json
to upgrade the vulnerable dependencies to a fixed version.You can read more about Snyk's upgrade and patch logic in Snyk's documentation. Each vulnerability advisory includes information about the vulnerable versions, and direct links to the available patches.
Note that this pull request only addresses the newly disclosed vulnerabilities mentioned above.
See the Snyk test report to review and remediate the full list of vulnerable dependencies.
Please check the changes in this PR to ensure they won't cause issues with your application.
Stay secure,
The Snyk team