You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your feature request related to a problem? Please describe.
SARIF is becoming the de-facto industry standard for SAST scanning results. Several tools already support it, like for example gitlab, github and more.
When adding the golangci-lint action on github I was missing an option to choose SARIF as output format to allow github to import any findings into the security tab or as a check result set in pullrequests.
Using the action in its current form does not seem to satisfyingly link findings to their actual locations in the code.
Describe the solution you'd like.
I'd like to see a SARIF output format (output.format: sarif) and ideally an option to define an output file name.
Describe alternatives you've considered.
Using the action in its current form and live with the shortcomings.
Search for an alternative tool.
Additional context.
No response
The text was updated successfully, but these errors were encountered:
Your feature request related to a problem? Please describe.
SARIF is becoming the de-facto industry standard for SAST scanning results. Several tools already support it, like for example gitlab, github and more.
When adding the golangci-lint action on github I was missing an option to choose SARIF as output format to allow github to import any findings into the security tab or as a check result set in pullrequests.
Using the action in its current form does not seem to satisfyingly link findings to their actual locations in the code.
Describe the solution you'd like.
I'd like to see a SARIF output format (
output.format: sarif
) and ideally an option to define an output file name.Describe alternatives you've considered.
Additional context.
No response
The text was updated successfully, but these errors were encountered: