Skip to content

chore: address zizmor findings and add github actions linting workflow - #352

Open
nscuro wants to merge 8 commits into
controlplaneio:masterfrom
nscuro:zizmor
Open

nscuro wants to merge 8 commits into
controlplaneio:masterfrom
nscuro:zizmor

Conversation

@nscuro

@nscuro nscuro commented Sep 23, 2026

Copy link
Copy Markdown

Addresses all findings reported by zizmor for the project's GitHub Actions workflows.

Adds a new workflow that runs zizmor to ensure no regressions are introduced later.

Addresses zizmor `artipacked` findings.

Signed-off-by: nscuro <nscuro@protonmail.com>
Addresses zizmor `unpinned-uses` findings.

Applied via:

```
GH_TOKEN="$(gh auth token)" zizmor --fix=all .github
```

Signed-off-by: nscuro <nscuro@protonmail.com>
Addresses zizmor's `excessive-permissions` findings by scoping permissions to jobs, and explicitly dropping permissions at the workflow-level.

Signed-off-by: nscuro <nscuro@protonmail.com>
zizmor flagged this step for cache poisoning risk and recommends configuring it as `lookup-only` (https://docs.zizmor.sh/audits/#remediation_5). However the step appears to be largely ineffective already since Actions cache is scoped to refs (in this case tags). A build for tag v0.1.5 thus wouldn't get cache hits from v0.1.4.

A fallback to `master` doesn't exist since nothing writes to the configured cache key for that branch. Opted to remove the step altogether.

Signed-off-by: nscuro <nscuro@protonmail.com>
Addresses zizmor's `cache-poisoning` finding. The cache gets populated from builds on `master`, thus posing a real poisoning risk for release builds.

Release builds will be slower but that should be fine given they're super infrequent.

Signed-off-by: nscuro <nscuro@protonmail.com>
Addresses zizmor `dependabot-cooldown` findings.

Signed-off-by: nscuro <nscuro@protonmail.com>
Signed-off-by: nscuro <nscuro@protonmail.com>
@nscuro
nscuro requested a review from 06kellyjac as a code owner September 23, 2026 12:40
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

To be consistent with existing comments.

Signed-off-by: nscuro <nscuro@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants