Obtain the triggering build workflows from provenances for static analysis
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 210
- Forks
- 36
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
We need to implement a new feature to obtain the GitHub Actions workflow that has triggered a build/replease from the SLSA provenance (or build command from the Witness provenance) and use that in the build checks instead of analyzing all the Actions. This would let us to use the most accurate workflows in the static analysis and get more benefit from the provenances if they are available.
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
The issue names no files, tests, or entry points; start by tracing the build checks and existing SLSA or Witness provenance handling. Done means the relevant triggering workflow or build command is obtained from available provenance and used for static analysis instead of analyzing all Actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100