Adding poutine SAST #2138
Adding poutine SAST #2138
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Signed-off-by: Hayden Parsons <[email protected]>
add upload for results.sarif
add upload for results.sarif Signed-off-by: Hayden Parsons <[email protected]>
Signed-off-by: Hayden Parsons <[email protected]>
|
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.
gave Poutine Write Permissions
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