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
Currently there is an option to generate the output in JSON format that basically print the result array in this part of the code when using the parameter "--json=filename"
Adding a new output handler using a new parameter "--sarif=filename" could allow to export the result using SARIF format, this will allow to upload the result to any tool that support the specification.
In a high level the new parameter "--sarif=filename" could generate a SARIF file like this example
I already did a small poc creating a new output handler, is not really a big change in the code, it is just creating a new handler similar to the one that generate the JSON format but using the SARIF json structure.
I would like to help with this issue and send a PR if the cloudsploit team think that this feature could be usefull to other people that is currently using this tool.
The text was updated successfully, but these errors were encountered:
Currently there is an option to generate the output in JSON format that basically print the result array in this part of the code when using the parameter "--json=filename"
Example:
Adding a new output handler using a new parameter "--sarif=filename" could allow to export the result using SARIF format, this will allow to upload the result to any tool that support the specification.
In a high level the new parameter "--sarif=filename" could generate a SARIF file like this example
The command to generate that output could be like:
I already did a small poc creating a new output handler, is not really a big change in the code, it is just creating a new handler similar to the one that generate the JSON format but using the SARIF json structure.
I would like to help with this issue and send a PR if the cloudsploit team think that this feature could be usefull to other people that is currently using this tool.
The text was updated successfully, but these errors were encountered: