Adding poutine SAST#2138
Conversation
Signed-off-by: Hayden Parsons <h2parson@Douglass-MacBook-Pro.local>
add upload for results.sarif
add upload for results.sarif Signed-off-by: Hayden Parsons <h2parson@Douglass-MacBook-Pro.local>
Signed-off-by: Hayden Parsons <h2parson@Douglass-MacBook-Pro.local>
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
mark as safe directory
Changed poutine output file
| - name: Configure as safe directory | ||
| run: git config --global --add safe.directory /__w/liboqs/liboqs | ||
| - name: poutine - Static Application Security Testing | ||
| uses: boostsecurityio/poutine-action@main |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
There was a problem hiding this comment.
See Pravek's comment above for details on how to fix this message.
There was a problem hiding this comment.
Does boostsecurityio/poutine-action itself have to be pinned to a specific version?
If so, I think this 16c6972a96ef3c8b4a151dd4b6da2ccd48ef736d is the right commit hash.
Of course, it will likely be much easier to just click a button if one exists.
gave Poutine Write Permissions
|
Should be superseded by #2213. |
This PR adds poutine to CI for static application security testing
This PR addresses issue #1866
When this feature was pushed it was observed that poutine ran as part of the CI routine which shows that the feature works
This PR does NOT change input/output behaviour of a cryptographic algorithm and does not change the list of algorithms available