Improve SARIF path handling and severity #686
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.
In SARIF output, which is used by GitHub to display security findings, we need to best represent the files found during directory scans so they may match files within a repository, this corrects one case and adds a number of test cases for different Grype invocations: cwd, relative, and absolute paths.
Additionally, we don't really need a lot of precision for the severity, so we now limit this to 1 decimal place.