Evaluate .net dependency scanner (time box research, value pro/con vs roll our own)
Problem to solve
Based on the goals of #217374 (closed)
We would like to know if there is an OSS .net core and/or .net framework OSS scanner that we can easily add to our solution to expand our supported languages or if we should write it ourselves
one that came up was: https://www.infoq.com/news/2020/02/Microsoft-Application-Inspector/
Feel free to look at others
Propose one or two OSS scanner to do a POC on for both .net core and .net framework, or note why you believe we should build this in house.
Intended users
Further details
Proposal
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Activity
added typefeature label
added to epic &2550 (closed)
changed milestone to %Backlog
added [deprecated] Accepting merge requests label
changed milestone to %13.0
changed milestone to %13.1
changed milestone to %13.2
added AST Leadership label
changed milestone to %13.3
changed milestone to %13.4
Moving this out of Dependency Scanning - Viable to Complete and sub-epic Expand Supported Languages and Packages Dependency Scanning because we have decided after Engineering research - Decide next language to add to Dependency Scanning that we are doing NuGet for MVC, additional enhancements belong in Dependency Scanning - Complete to Loveable.
cc @gonzoyumo @david
changed milestone to %Backlog
removed AST Leadership label
changed epic to &2725
changed epic to &3754
added Enterprise Edition GitLab Ultimate labels
added sectionsec label
We are closing this issue automatically because it was created over a year ago and does not seem to have been picked up yet.
If you're reading this and feel like this issue is still relevant, please re-open it and apply the secureparked label to it.
added stale label
