refactor the OSV scanner from the ground up #1124
Merged
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 is a complete refactoring of the OSV scanner. The OSV scanner is written in Go, so there is no reason for us to not use it a s a library so that we can configure it more easily and not having to parse its output from a file but directly use the data structures from it and convert them into OCSF.
Under normal circumstances, OSV scanner scans the entire repository for dependency files and outputs the results. We are not interested in tackling every single language out there, we are interested in producing good results, so for the time being we dedicate the scanner to Go, JS and Elixir, with more to be added as time goes. The results should always contain the lines of the dependency file where a vulnerable file is declared