patch: Add lockfile-lint #16
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
Signed-off-by: Vipul Gupta (@vipulgupta2048) <vipulgupta2048@gmail.com>
@vipulgupta2048 Could you please provide a reference to this vulnerability? |
LucianBuzzo
approved these changes
Feb 7, 2023
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.
Recently, I came to know about a potenial vulnerablity that can be introduced through NPM lockfiles. All of our project use NPM or yarn for package management and I think this shouldn't be ignored. Thankfully the issue can be easily mitigated by having an additional lockfile lint check: https://github.com/lirantal/lockfile-lint/tree/master/packages/lockfile-lint
FD: https://www.flowdock.com/app/rulemotion/r-beginners/threads/AiikeXdBHQ8WcpZaAlYUILAsb8w
Signed-off-by: Vipul Gupta (@vipulgupta2048) vipulgupta2048@gmail.com