litestar-org / litestar-org/project-template
ci: adopt zizmor for GitHub Actions security
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
## Context
[`zizmor`](https://github.com/woodruffw/zizmor) is a static analysis tool for GitHub Actions workflows that catches injection, excessive permissions, unpinned actions, and other CI supply-chain issues.
## Proposed tasks
- [ ] Add a `zizmor` job (or pre-commit hook) scanning `.github/workflows/`
- [ ] Triage & fix initial findings (likely: pin actions to SHAs, tighten `permissions:`)
- [ ] Wire into CI as a required check
## References
- [zizmor docs](https://docs.zizmor.sh/)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the workflows under .github/workflows/ and the zizmor documentation. Add a zizmor scan, address its initial findings such as action pinning and permissions, and make the scan a required CI check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100