feat: Generate SLSA provenance #399
Open
Conversation
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
|
/cc @wagoodman @kzantow |
|
Thanks very much for this @laurentsimon -- it might be a week or so before I can get to review this in detail and provide a few tweaks, but it looks like a great start! I'll ping you on one of our shared Slack workspaces if questions come up. |
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.
Following to our discussion from last week, this is the PoC to generate SLSA provenance.
We're working on verification support in the next couple weeks, but it should not block you from iterating if you need.
We're also working on documentation. In the meantime, don't hesitate to ask questions.
Feel free to keep a friction log, we appreciate feedback!
Thanks!