This repository has been archived by the owner on Jun 21, 2022. It is now read-only.
Feat: Created analyzer for NuGet lockfiles. #139
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
Signed-off-by: Johannes Tegnér <[email protected]>
Johannestegner
force-pushed
the
feature/nuget-analyzer
branch
from
7d817d6 to
3decfdd
Compare
knqyf263
approved these changes
Oct 28, 2020
|
Thanks a lot!! |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This pull requests include a new analyzer for NuGet
packages.lock.jsonfiles.It's basically the same as the other analyzers, but makes use of the NuGet parser which is included in the following
go-dep-parserpull request.For reference, feature request issue can be found here: aquasecurity/trivy#681