{{ message }}
Fix lodash vulnerability: Prototype Pollution - #238
Merged
Merged
Conversation
bajtos
changed the title
bajtos
approved these changes
May 10, 2018
bajtos
left a comment
bajtos
left a comment
Member
There was a problem hiding this comment.
Thank you for the pull request! I have edited the commit message to better describe what is being fixed. Let's wait for CI results before landing.
Member
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
I was using
loopback-component-explorer@4.3.0and having a NSP vulnerability warning (Ref: https://nodesecurity.io/advisories/577)These are the compatibility-warnings for upgrading
lodashfrom v3 to v4 (https://github.com/lodash/lodash/wiki/Changelog#compatibility-warnings)