fix Node.js package vulnerabilities #12
Open
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
Just a simple
npm audit fix
can be marvelous and fix all that nasty vulnerabilities in one
step.
|
Just a quick question since there has been no reaction here for almost a month: Did you by any chance just fail to notice this pull request? Or is there some other reason why there has been no reaction so far? Please let me know if there is anything missing in this pull request or if there is anything I can do on my side to speed things up. |
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.
If the current master branch is checked out, then
npm auditreports almost 16,000 vulnerabilities in the package dependencies. This pull request fixes those vulnerabilities (commit 68e73e6). Additionally, it updates the package versions (commit 106a448).