diff options
| author | Leitwolf11 | 2026-10-10 20:23:52 +0300 |
|---|---|---|
| committer | Leitwolf11 | 2026-10-10 20:23:52 +0300 |
| commit | ba6cbc4e6fc71f7b2240f9c42f1124dc2e9b6532 (patch) | |
| tree | 4c95baf610c3034206537c8c7a231372b3a45403 /tests/Progmasoft/Generators.tests.cpp | |
| parent | 00bd15ded1dd732472156aece844e7696454bd3a (diff) | |
| download | catch3-ba6cbc4e6fc71f7b2240f9c42f1124dc2e9b6532.tar.gz | |
Add workflow, repository and dependency analysis
zizmor audits the workflows themselves for what makes a workflow
unsafe, and uploads what it finds to code scanning. Its first run here
found one thing, 11 times: a checkout that leaves the job's token in
the checked-out repository, where any later step can read it. No
workflow pushes or needs the token after the checkout, so every checkout
now sets persist-credentials to false, and zizmor reports nothing.
OpenSSF Scorecard grades how the repository is kept: branch protection,
pinned dependencies, token permissions and the like. It runs on the
default branch and weekly and uploads its findings to
code scanning.
Dependency Review fails a pull request that adds or changes a dependency
with a known vulnerability of high severity or worse. Dependabot watches
what is already there; this holds what comes in.
Every new action is pinned to a commit, each job names the permissions
it needs, and no new workflow has a default permission.
Two steps of the Windows build ran in the CMD shell, which zizmor cannot
read into; they run in PowerShell now, with the same commands and the
processor count taken from the environment.
Diffstat (limited to 'tests/Progmasoft/Generators.tests.cpp')
0 files changed, 0 insertions, 0 deletions