Added CodeQL scan and Clang Static Analyzer to workflows #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
The issues discussed in #18, #19, #20 and #21 were discovered by using CodeQL security scanning and the Clang Static Analyzer. This PR adds two workflows to automatically perform CodeQL and Clang Static Analyzer scans on bc-sskr.
CodeQL security scan results can be seen in the "Security" tab of the this repo.
If this PR is of any use then similar can be done for bc-shamir.
Note: This PR does not make any changes to code.
In future I may look to outputing the Clang Static Analyzer ourput in SARIF format and uploading to GitHub:
See here: https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github
Then all analyzer output can be viewed and managed in one place on the Security page of the repo.