in-toto / in-toto/github-action
Document SLSA level for build attesations
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Hey!
Very cool project, and we were curious about your SLSA leveling and roadmapping.
I believe this achieves SLSA 2 when creating attestations for a command that produces a build artifact, since it creates signed attestations with the provided key (and upcoming, Fulcio issued certificates).
I was curious about adding a build demo to achieve SLSA 2, and also, if there's a roadmap or way to achieve SLSA 3. We are also creating builders on slsa-framework/slsa-github-generator and some follow a similar model as this one, but we achieve SLSA 3 through some further isolation requirements.
I'd be happy to add a PR with some README documentation about SLSA. Let me know!
cc @laurentsimon @joshuagl
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the README and review how the action creates signed attestations for commands that produce build artifacts. Document the applicable SLSA level, add the proposed build demo, and explain the roadmap or isolation requirements for reaching SLSA 3. No tests or other files are mentioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100