356c1f8336
chore: Set permissions for GitHub actions
...
Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.
- Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
[Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ )
Signed-off-by: neilnaveen <42328488+neilnaveen@users.noreply.github.com>
2022-06-07 14:32:11 +01:00
c8810277bb
Update Coverity settings
2022-04-22 02:22:29 +02:00
7099a6dca1
[atomic] Remove old Intel primitives implementation
2021-02-20 15:20:06 -07:00
11ae45f6eb
[ci] Don't run cov-analyze
...
https://stackoverflow.com/a/59353318
2020-07-22 17:52:16 +04:30
f65a8a33b6
[ci] run cov-analyze
...
apparently we have to run that also ourselves, let's see
2020-07-19 18:13:48 +04:30
2c1d699409
[ci] use clang for cov-build
...
to be honest this is done as a let's see what
happens move but the background is coverity
reveals more things for Firefox project and there
should be an interesting reason for it.
2020-07-13 20:26:57 +04:30
8ba8980222
[ci] enable experimental apis in coverity scan
2020-04-28 20:14:17 +04:30
d63ee13a2a
[ci] enable more on coverity
2020-04-28 20:01:11 +04:30
1801489b49
[ci] Add coverity scan bot
2020-04-28 18:47:39 +04:30
neilnaveen
Khaled Hosny
Behdad Esfahbod
Ebrahim Byagowi