diff options
| author | Leitwolf11 | 2026-10-10 20:23:08 +0300 |
|---|---|---|
| committer | Leitwolf11 | 2026-10-10 20:23:08 +0300 |
| commit | 525f3c0566247bbb6a81b5a2e1488147688c089a (patch) | |
| tree | 2097fdabc9d3cdc29bf26e434178e50e54548768 /apps/api/appsettings.Development.json | |
| parent | 111a6175e0a92808ddc2a47088fa9858001eeed9 (diff) | |
| download | progmaweb-525f3c0566247bbb6a81b5a2e1488147688c089a.tar.gz | |
Add workflow and repository 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, 6 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, publishes its score and uploads its findings to
code scanning.
Every new action is pinned to a commit, each job names the permissions
it needs, and no new workflow has a default permission.
Diffstat (limited to 'apps/api/appsettings.Development.json')
0 files changed, 0 insertions, 0 deletions