Update nsp and rc to fix vulnerabilities #82
Merged
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
| @@ -29,7 +29,7 @@ | |||
| "npmlog": "^4.0.1", | |||
| "os-homedir": "^1.0.1", | |||
| "pump": "^2.0.1", | |||
| "rc": "^1.1.6", | |||
| "rc": "^1.2.7", | |||
There was a problem hiding this comment.
Just fyi. This is technically not needed in order to get updated rc.
|
This will mean a new major version for next release. |
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.
There are 3 vulnerabilities related to nsp and rc dependencies:
https://nodesecurity.io/advisories/593 in https-proxy-agent
https://nodesecurity.io/advisories/566 in deep-extend and hoak
https://nodesecurity.io/advisories/532 in moment
Since nsp 3.2 dropped support for Node.js v4 for which the EOL date is April 30th i also removed support for Node 4 in the project