-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added new Nuget packages.config analyzer (Nugetconf) #1406
Conversation
Can one of the admins verify this patch? |
@doshyt - this is one of the most complete and highest quality PRs we've seen. From clean, documented code to updating the user documentation. Thank you for adding the configuration to all of the implementations (maven, cli, ...). What really surprised me is that you even noticed that you needed to update the dependencycheck-base-suppression.xml to filter out some obvious FP. Thank you! |
@jeremylong - thanks for the good words! I also noticed that there is a lot of duplication in XPath parsing implementations between Nuspec, MSBuild and packages.config analyzers. Probably, it can be simplified and merged into the same parser that implements searches for these analyzers. I would love to work on it next. |
Fixes Issue
Adds support of .NET packages.config dependency format. This format is a popular way to declare dependencies for MSBuild projects without including them into *.csproj files or using *.nuspec files.
Description of Change
Created a new analyzer "Nugetconf" using the existing Nuspec and MSBuild analyzers as inspirations; marked it as experimental. Updated settings, CLI options, various documentation files and added test cases.
Have test cases been added to cover the new functionality?
Yes