Update lru-memoizer to 2.0.1 #106
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
Snyk.io detects vulnerabiliity in unused component of `lodash` via `lru-memorizer`. `lru-memorizer` updated to remove vulnerable component. Refer to GitHub issue [#86]
|
Checked with @jfromaniello that this is a safe merge. Internals changed, interface did not. |
damieng
approved these changes
Aug 26, 2019
Closed
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.
Description
lru-memorizer had unused dependency on lodash being detected by snyk.io
This was removed here jfromaniello/lru-memoizer@c2cf36d
References
Raised in Github issue [#86]
Testing
Existing test coverage runs successfully
No change to exisiting test coverage required.
-] This change adds test coverage for new/changed/fixed functionalityChecklist
x] I have added documentation for new/changed functionality in this PR or in auth0.com/docsx] All active GitHub checks for tests, formatting, and security are passing?] The correct base branch is being used, if notmaster