Bumped ip from v1.1.8 to v2.0.1 #160
Closed
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
added 2 commits
February 20, 2024 12:15
…dit to fix vulnerable packages
bitcode001
changed the title
|
I sometimes question these alarmist PRs: |
jetersen
changed the title
|
fixed in #163 Your package-lock.json changes looked odd. |
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.
Bumped ip from v1.1.8 to v2.0.1 to fix vulnerability issues and npm audit to fix vulnerable packages.
ipv1.1.8 was flagged to be highly vulnerable and was quickly actioned by the team "node-ip"
🚨 HIGH Severity Vulnerability: Package unsafe for use as of v1.1.8 🚨