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
I believe it would be very interesting if the project had support for SARIF [1]. SARIF is already a strong industry standard and I believe that all the tools that Husky uses already have this option.
With that, it would be a little simpler to integrate new SAST/SCA tools in Husky. We could also have a SARIF output to help make the information that Husky generates easy to migrate to other platforms. For example, with this we can drastically reduce the codes used to map the fields in the output for each tool.
Hi folks!
I believe it would be very interesting if the project had support for SARIF [1]. SARIF is already a strong industry standard and I believe that all the tools that Husky uses already have this option.
With that, it would be a little simpler to integrate new SAST/SCA tools in Husky. We could also have a SARIF output to help make the information that Husky generates easy to migrate to other platforms. For example, with this we can drastically reduce the codes used to map the fields in the output for each tool.
Thanks!
[1] - https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.pdf
The text was updated successfully, but these errors were encountered: