chore: fix zizmor findings in workflows - #431
Merged
Merged
Conversation
|
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:
For more information about GitHub Code Scanning, check out the documentation. |
wimspaargaren
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why zizmor?
zizmor is a static analysis tool for GitHub Actions workflows. It catches security misconfigurations that are easy to miss in code review but are commonly exploited in supply-chain attacks.
Findings addressed
unpinned-uses— Actions pinned to a tag (e.g.@v1) can silently change if the tag is force-pushed or hijacked. Pinning to an immutable commit SHA guarantees the exact code that ran in CI today is the same code that runs tomorrow, even if the upstream repo is compromised.artipacked— By defaultactions/checkoutpersists a GitHub token in the local git config so that subsequentgitcommands can authenticate. If any later step in the job (or a transitive action) exfiltrates the workspace, it gets the token for free. Settingpersist-credentials: falseremoves the token after checkout unless it is explicitly needed.dependabot-cooldown— Without a cooldown, Dependabot can open PRs for a newly published package version within minutes of release. A short window is a known vector for dependency-confusion and typosquatting attacks where a malicious version is published and auto-merged before the community notices. Requiring a minimum 7-day cooldown gives the ecosystem time to vet new releases.Validation