chore: use zizmor to validate and report problems in github actions
- Dominant language
- Python
- Stars
- 5.9k
- Forks
- 600
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 38
Description
Detect and report problems (ie. too broad permission, actions not bound to immutable commits etc.) based on the following workflow:
https://github.com/apache/lucene/blob/main/.github/workflows/actions.yml
background:
https://github.com/dlt-hub/dlt/pull/3470#discussion_r2627534736
essence of the workflow:
* use zizmor to detect problems
* use SARIF to post findings to github to be reported with other vulns
followup:
add to all our actively used public and private repos
Contributor guide
Research direction
Start with .github/workflows/actions.yml and the linked background discussion; identify where zizmor validation belongs and how findings should be emitted as SARIF for GitHub reporting. Done means the workflow detects issues such as broad permissions or mutable action references and publishes those findings alongside other vulnerabilities.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100