cache npmjs package lookups in a local file#43
Open
adhintz wants to merge 1 commit intovisma-prodsec:mainfrom
Open
cache npmjs package lookups in a local file#43adhintz wants to merge 1 commit intovisma-prodsec:mainfrom
adhintz wants to merge 1 commit intovisma-prodsec:mainfrom
Conversation
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
1 participant
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.
I'm scanning a large number of repositories that have npmjs package files. By caching the available packages, it runs substantially faster, avoids npmjs rate-limiting, and reduces load on their service.
Please let me know if you'd prefer anything changed in the PR. I'm inexperienced with golang.
If this general approach looks good to you, I'd be happy to expand it to the other package systems.