Sigstore
sigstore.dev
- Free plan
- Open source
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What Sigstore is
Sigstore is a free, open source project for signing and verifying software artifacts as part of software supply chain security. It covers release files, container images, binaries, software bills of materials and more. Developers use ephemeral signing keys, avoiding the need to manage signing keys, while signing events are recorded in a tamper-resistant public log for auditing. Its components include Cosign, Fulcio, Rekor, OpenID Connect and Policy Controller. Cosign signs and verifies artifacts and stores signatures in an OCI registry; Fulcio issues temporary certificates to authorized identities, and Rekor maintains searchable signed metadata. OpenID Connect authenticates users through providers such as GitHub and Google. Sigstore offers GitHub Actions and documents GitLab CI installation, with official language clients for Go, Java, JavaScript, Python, Ruby and Rust. The trust root uses The Update Framework and is maintained by five keyholders from companies and academic institutions. It is available for Linux, macOS, Windows, API and self-hosted environments. Community support is available through Slack and GitHub issues.
Who it suits
Sigstore suits developers and software providers who need to sign and verify artifacts, and package managers working to integrate signing and verification into tooling or registries. It is free to use.
Good to know, and what to watch
- Covers container images, binaries and software bills of materials
- Ephemeral keys remove key-management work
- Public log supports auditing signing events
- Official clients span six programming languages
- GitHub Actions and GitLab CI guidance are available
- Cosign has no API stability guarantees
- Cosign does not follow semantic versioning
- Cosign is not recommended for application integration
Plans
Every plan and priceFree
Public-good Sigstore service
Free plan
Getting started
- Open the Sigstore website and choose an API, Linux, macOS, Windows, or self-hosted environment
- Authenticate through an OpenID Connect provider such as GitHub or Google
- Install Cosign through the provided GitHub Actions workflow or follow the GitLab CI installation documentation
- Use Cosign to sign or verify artifacts and store signatures in an OCI registry
- Connect signing and verification workflows with package tooling or registries
Limits to check
Cosign has no API stability guarantees, does not use semantic versioning, and is not recommended for application integration because of its dependencies.
The verdict
Sigstore brings signing, identity and public audit records together for software artifacts. The Cosign integration caveat matters for application developers: its API is not stable, and the project does not recommend that use.
Questions people ask
Is Sigstore free?
Yes. The Free plan costs nothing and is free for developers and software providers.
What does Sigstore sign?
It supports release files, container images, binaries, software bills of materials, and other artifacts.
Which CI integrations are available?
Sigstore provides GitHub Actions for generating signatures and installing Cosign, and documents GitLab CI installation.
Which programming languages have official clients?
Official clients are available for Go, Java, JavaScript, Python, Ruby, and Rust.
How are users authenticated?
Sigstore uses OpenID Connect with identity providers such as GitHub and Google.
Where can teams get support?
Community support is available through Slack, and users can open GitHub issues in the relevant repository.
What the maker publishes
- API coverage
- The documented API policy covers Fulcio and Rekor client APIs, Cosign features, the sigstore client library and the cosign OCI library. source
- API stability
- Sigstore classifies interfaces as Experimental, Beta or Generally Available, with best-effort deprecation notice periods of zero, two months or six months respectively. source
- Artifact coverage
- Sigstore supports signing and verifying release files, container images, binaries, software bills of materials and more. source
- CI integrations
- Sigstore provides GitHub Actions for generating signatures and installing Cosign, and documents GitLab CI installation. source
- Components
- Sigstore combines Cosign, Fulcio, Rekor, OpenID Connect and Policy Controller technologies. source
- Cosign
- Cosign signs and verifies containers and other artifacts and stores signatures in an OCI registry. source
- Cosign
- Cosign is the command-line tool for signing and verifying containers and other artifacts, with signatures stored alongside artifacts in OCI registries. source
- Custom infrastructure
- Cosign can be configured to use privately operated Fulcio, Rekor, certificate-transparency and timestamp services with custom trust roots. source
- Documentation
- The project publishes user quickstarts, component documentation, developer documentation, certificate-authority material and troubleshooting guidance. source
- Ephemeral keys
- Its signing workflow uses short-lived or ephemeral keys, reducing the need for developers to manage persistent private keys. source
- Founded
- 2021 source
- Fulcio
- Fulcio is a free root certification authority that issues temporary certificates to authorized identities and publishes them in Rekor. source
- Fulcio
- Fulcio is a free certificate authority that issues temporary certificates to authenticated identities and publishes certificate information through Rekor. source
- GitHub Actions integration
- Sigstore publishes a Python signing action and a Cosign installer action for CI workflows. source
- Governance
- Sigstore is operated as a public-good, nonprofit project within the Open Source Security Foundation ecosystem. source
- Identity
- Sigstore uses OpenID Connect to authenticate users through identity providers such as GitHub and Google. source
- Independent company profile
- LinkedIn describes Sigstore as a London-based nonprofit public-good signing service with 2–10 employees and a 2021 founding year. source
- Independent ecosystem evidence
- The Linux Foundation said Sigstore had been used by projects including Kubernetes and received support from Chainguard, Cisco, HPE, Google, Red Hat and VMware in 2021. source
- Independent usage evidence
- GitHub documents Sigstore Policy Controller deployment with two Helm charts and OCI-attached Sigstore Bundles for image attestations. source
- Integration limitation
- Cosign has no API stability guarantees, does not follow semantic versioning, and is not recommended for application integration because of its dependencies. source
- Keyless verification
- Verification checks the artifact signature, certificate identity, Sigstore trust root and Rekor inclusion proof together. source
- Key management
- Sigstore generates signatures with ephemeral signing keys, so developers do not need to manage keys. source
- Kubernetes policy
- The Policy Controller is a Kubernetes admission controller that can require valid container signatures or attestations before deployment. source
- Language clients
- Official language clients are available for Go, Java, JavaScript, Python, Ruby and Rust. source
Checked against the maker's pages on 15 Oct 2026.