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
Vulnerabilities that will be fixed
With an upgrade:
Why? Has a fix available, CVSS 7.1
SNYK-JS-GRUNT-597546
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-450202
Why? Proof of Concept exploit, CVSS 6.3
SNYK-JS-LODASH-567746
Why? CVSS 9.8
SNYK-JS-LODASH-590103
Why? Proof of Concept exploit, CVSS 7.3
SNYK-JS-LODASH-608086
Why? CVSS 7.3
SNYK-JS-LODASH-73638
Why? CVSS 4.4
SNYK-JS-LODASH-73639
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
SNYK-JS-MARKDOWNIT-459438
Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
SNYK-JS-MINIMIST-559764
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
npm:clean-css:20180306
Why? Mature exploit, Has a fix available, CVSS 5.1
npm:concat-stream:20160901
Why? Has a fix available, CVSS 3.7
npm:debug:20170905
Why? CVSS 6.3
npm:lodash:20180130
Why? Has a fix available, CVSS 3.7
npm:ms:20170412
Why? CVSS 7.5
npm:qs:20170213
Why? Has a fix available, CVSS 5.3
npm:semver:20150403
(*) Note that the real score may have changed since the PR was raised.
Commit messages
Package name: grunt
The new version differs by 40 commits.See the full diff
Package name: grunt-contrib-csslint
The new version differs by 11 commits.See the full diff
Package name: grunt-contrib-cssmin
The new version differs by 6 commits.See the full diff
Package name: grunt-contrib-htmlmin
The new version differs by 14 commits.See the full diff
Package name: grunt-contrib-qunit
The new version differs by 17 commits.See the full diff
Package name: grunt-contrib-watch
The new version differs by 4 commits.See the full diff
Package name: markdown-it
The new version differs by 115 commits.See the full diff
With a Snyk patch:
Why? Has a fix available, CVSS 3.7
npm:debug:20170905
Why? Has a fix available, CVSS 6.3
npm:hoek:20180212
Why? CVSS 6.3
npm:lodash:20180130
Why? Has a fix available, CVSS 7.5
npm:minimatch:20160620
Why? Has a fix available, CVSS 3.7
npm:ms:20170412
Why? Has a fix available, CVSS 5.1
npm:request:20160119
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