Code Signing Policy¶
Stillwater binaries are code-signed through the SignPath Foundation free code-signing program for open-source projects.
Free code signing provided by SignPath.io, certificate by SignPath Foundation.
Signing roles¶
The following roles apply to Stillwater's signing process, as defined by SignPath's role model.
| Role | Responsibility | Member |
|---|---|---|
| Author | Commits code to the repository without requiring additional review | Jesse Slaton (@sydlexius) |
| Reviewer | Reviews changes from non-committers and provides code review feedback | Jesse Slaton (@sydlexius) |
| Approver | Approves each signing request before a signed binary is released | Jesse Slaton (@sydlexius) |
Automated review tools (CodeRabbit, Codoki) assist the human review process but do not hold any signing role. All signing decisions are made by the human Approver above.
Release and signing process¶
Every release follows this process:
- A release build is produced by CI (GitHub Actions) from a tagged commit on the
mainbranch. - Checksums are generated for each build artifact.
- A signing request is submitted to SignPath.io.
- A human Approver (listed above) manually reviews and approves the signing request. No release is signed or published automatically without this step.
- Signed artifacts are published to the GitHub Releases page.
Verifying a release¶
Each release ships with Sigstore-signed checksums and SLSA build provenance. See the binary install guide for verification instructions.
Privacy¶
See the Privacy Policy for a full description of what Stillwater transmits over the network and what it does not collect.