#65 - Reader for Snyk and Semgrep SARIF files #67
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi @davewichers,
as mentioned via Mail, this is my current state. It can be merged and I can do my refactoring in another PR.
This solves #65 and supports Semgrep SARIF. For some reason, Snyk JSON and SARIF seems to be the same export, just with different file ending (or the one who provided the file used the wrong file ending). So BenchmarkUtils should already be able to parse Snyk SARIF file when changing ending to
.sarifinstead of.json. I refactored the class and removed the check for file ending, so it does not matter which type is provided. 🤷♂️Sascha