Provide a way to verify release integrity
Open
Nobody has claimed this yet.
enhancement
release
- Dominant language
- Go
- Stars
- 9.6k
- Forks
- 962
- Avg merge
- 23h 27m
- Merged PRs (30d)
- 48
Description
Today we have a checksum file + signature, however, we do not publish the key. We should either publish the key or replace this mechanism (maybe with a sigstore workflow).
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 locating the current checksum and signature publishing workflow. Compare publishing the verification key with the proposed sigstore workflow, and define what a user must be able to verify for the work to be done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100