as mentioned via Mail, this is my current state. It can be merged and I can do my refactoring in another PR.
This solves https://github.com/OWASP-Benchmark/BenchmarkUtils/issues/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 .sarif instead of .json. I refactored the class and removed the check for file ending, so it does not matter which type is provided. 🤷♂️
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 https://github.com/OWASP-Benchmark/BenchmarkUtils/issues/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