microsoft / microsoft/component-detection
Sign Component Detection GitHub releases
Open
@FernandoRojo is already working on this.
Since May 21, 2024.
status:requirements
type:ci
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
In accordance with OpenSSF's recommendations, we should be cryptographically signing our GitHub releases with a GPG key.
* OpenSSF Guidance: https://github.com/ossf/scorecard/blob/4edb07802fdad892fa8d10f8fd47666b6ccc27c9/docs/checks.md#signed-releases
* Doc on signing releases from debian: https://wiki.debian.org/Creating%20signed%20GitHub%20releases
We can perhaps use the cert from OneCert when we complete #652
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.
Assessment
This issue has not been assessed yet.