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 created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR
Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
Adding or updating a Snyk policy (.snyk) file; this file is required in order to apply Snyk vulnerability patches.
Find out more.
Vulnerabilities that will be fixed
With an upgrade:
Why? Has a fix available, CVSS 8.1
SNYK-JS-AJV-584908
Why? CVSS 5.9
SNYK-JS-JSYAML-173999
Why? CVSS 8.1
SNYK-JS-JSYAML-174129
Why?
SNYK-JS-MARKED-174116
Why?
SNYK-JS-MARKED-451540
Why?
SNYK-JS-MERGE-1040469
Why?
SNYK-JS-MERGE-1042987
Why?
SNYK-JS-MERGE-72553
Why? Proof of Concept exploit, CVSS 5.6
SNYK-JS-MINIMIST-559764
Why?
SNYK-JS-NODEFETCH-674311
Why?
SNYK-JS-NPM-537603
Why?
SNYK-JS-NPM-537604
Why?
SNYK-JS-NPM-537606
Why?
SNYK-JS-NPM-575435
Why?
SNYK-JS-NPMUSERVALIDATE-1019352
Why? CVSS 4.4
npm:chownr:20180731
Why? Has a fix available, CVSS 6.3
npm:hoek:20180212
Why?
npm:npm:20180222
(*) Note that the real score may have changed since the PR was raised.
Commit messages
Package name: david
The new version differs by 14 commits.See the full diff
Package name: isomorphic-fetch
The new version differs by 12 commits.See the full diff
Package name: merge
The new version differs by 29 commits.See the full diff
Package name: meta-marked
The new version differs by 5 commits.See the full diff
Package name: mkdirp
The new version differs by 4 commits.See the full diff
Package name: npm
The new version differs by 250 commits.See the full diff
Package name: prop-types
The new version differs by 23 commits.See the full diff
With a Snyk patch:
Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
SNYK-JS-LODASH-567746
Why? Has a fix available, CVSS 3.7
npm:debug:20170905
Why? Has a fix available, CVSS 7.3
npm:extend:20180424
Why? Has a fix available, CVSS 6.3
npm:hoek:20180212
Why?
npm:marked:20170907
Why?
npm:mime:20170907
Why?
npm:qs:20140806-1
Why?
npm:request:20160119
Why? Mature exploit, Has a fix available, CVSS 5.2
npm:stringstream:20180511
Why? Has a fix available, CVSS 5.9
npm:tough-cookie:20170905
Why? Proof of Concept exploit, Has a fix available, CVSS 5.1
npm:tunnel-agent:20170305
(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic