[Snyk] Security upgrade npm from 5.6.0 to 6.2.0 #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-LODASH-6139239
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR was automatically created by Snyk using the credentials of a real user.
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? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.01055, Social Trends: No, Days since published: 0, Reachable: No, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.83, Score Version: V5
SNYK-JS-LODASH-6139239
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: npm
-
6.2.0 - 2018-07-14
-
6.2.0-next.1 - 2018-07-05
-
6.2.0-next.0 - 2018-06-29
-
6.1.0 - 2018-05-24
-
6.1.0-next.0 - 2018-05-17
-
6.0.1 - 2018-05-10
-
6.0.1-next.0 - 2018-05-04
-
6.0.0 - 2018-04-24
-
6.0.0-next.2 - 2018-04-21
-
6.0.0-next.1 - 2018-04-13
-
6.0.0-next.0 - 2018-03-23
-
5.10.0 - 2018-05-11
-
5.10.0-next.1 - 2018-05-07
-
5.10.0-next.0 - 2018-04-13
-
5.9.0-next.0 - 2018-03-23
-
5.8.0 - 2018-03-23
-
5.8.0-next.0 - 2018-03-13
-
5.7.1 - 2018-02-22
-
5.7.0 - 2018-02-21
-
5.6.0 - 2017-11-28
from npm GitHub release notesIn case you missed it, we moved!. We look forward to seeing future PRs landing in npm/cli in the future, and we'll be chatting with you all in npm.community. Go check it out!
This final release of
npm@6.2.0includes a couple of features that weren't quite ready on time but that we'd still like to include. Enjoy!FEATURES
244b18380#20554 add support for --parseable output (@ luislobo)7984206e2#12697 Add newsign-git-commitconfig to control whether the git commit itself gets signed, or just the tag (which is the default). (@ tribou)FIXES
4c32413a5#19418 Do not useSETto fetch the env in git-bash or Cygwin. (@ gucong3000)DEPENDENCY BUMPS
d9b2712a6request@2.81.0: Downgraded to allow better deduplication. This does introduce a bunch ofhoek-related audit reports, but they don't affect npm itself so we consider it safe. We'll upgraderequestagain oncenode-gypunpins it. (@ simov)2ac48f863node-gyp@3.7.0(@ MylesBorins)8dc6d7640cli-table3@0.5.0:cli-table2is unmaintained and requiredlodash. With this dependency bump, we've removedlodashfrom our tree, which cut back tarball size by another 300kb. (@ Turbo87)90c759feenpm-audit-report@1.3.1(@ zkat)4231a0a1eAddcli-table3to bundleDeps. (@ iarna)322d9c2f1Makestandardhappy. (@ iarna)DOCS
5724983ea#21165 Fix some markdown formatting in npm-disputes.md. (@ hchiam)738178315#20920 Explicitly state that republishing an unpublished package requires a 72h waiting period. (@ gmattie)f0a372b07Replace references to the old repo or issue tracker. We're at npm/cli now! (@ zkat)6.2.0-next.1
6.2.0-next.0
6.1.0
6.1.0-next.0
6.0.1
6.0.1-next.0
6.0.0
5.10.0
5.10.0-next.1
Commit messages
Package name: npm
The new version differs by 250 commits.See the full diff
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
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Prototype Pollution