Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Sigstore is a set of free services that make software signing practical: a certificate authority that issues short-lived certificates against an identity, and a public transparency log of every signature.

What Is Sigstore?
Sigstore exists because almost nobody signs software. Not through negligence — because conventional code signing requires generating a long-lived private key, storing it somewhere a build pipeline can read it, keeping it from everyone who should not have it, and revoking everything if it leaks. Faced with that, most projects skip signing entirely.
Sigstore removes the key. You prove who you are with an identity you already have, receive a certificate valid for about ten minutes, sign, and throw the key away. It is an Open Source Security Foundation project, and the public instance is free to use.
Fulcio is a certificate authority. Present a valid OpenID Connect token — from GitHub, Google, Microsoft, GitLab, or your own provider — and it issues a short-lived X.509 certificate that binds your ephemeral public key to the identity in that token. For a GitHub Actions workflow the identity is precise: repository, workflow file, branch, and trigger.
Rekor is an append-only transparency log, built on a Merkle tree, that records every signature with a trusted timestamp. Entries cannot be removed or altered without detection. This is what makes short-lived certificates workable: verification does not ask whether the certificate is valid now, it asks whether the signature was made while it was valid, and the log proves when.
Cosign is the client most people use, signing container images, SBOMs, and attestations. Gitsign does the same for git commits. Policy-controller enforces signature requirements at Kubernetes admission. The root of trust is distributed using The Update Framework, so clients can establish which Fulcio and Rekor keys to believe without trusting a single static certificate.
The model owes a great deal to Certificate Transparency, and the security property is similar. An attacker who compromises a maintainer’s identity provider account can sign a malicious release — but the act is permanently and publicly recorded, with a timestamp and the identity used. The maintainer, or anyone monitoring, can see a signature they did not make.
Detection rather than prevention is a deliberate trade. It is also why you should treat the log as something to monitor, not merely to write to.
Adoption moved quickly after general availability in October 2022:
The practical result is that verifying a dependency’s origin is becoming something you can actually do, rather than a theoretical possibility.
A Sigstore signature proves that a particular identity signed a particular artefact at a particular time. It makes no claim about the code. A compromised pipeline produces valid signatures on malicious output, which is why signing belongs alongside SLSA provenance, hardened builders, and reproducible builds rather than in place of them.
Keyless signing also means trusting an external identity provider and, on the public instance, services operated by the OpenSSF. Verification requires reaching Rekor unless you bundle the log entry with the artefact, which matters in restricted networks. Organisations that cannot accept either dependency can run private Fulcio and Rekor instances, and several vendors package exactly that.
Finally, signing changes nothing until something refuses unsigned artefacts. Verification at admission, in the package installer, or in the deployment pipeline is where the control lives. An organisation that signs everything and verifies nothing has produced an audit trail, not a defence against a supply chain attack.
A key pair is still generated, but it exists only for the few seconds of the signing operation and is then discarded. Trust rests on the identity you proved to Fulcio and on the timestamped record in the Rekor transparency log, which shows the signature was made while the certificate was valid. There is no long-lived secret to steal, rotate, or accidentally commit.
Rekor is an append-only public log of signing events, built on a Merkle tree so entries cannot be changed or removed undetected. It provides the trusted timestamp that makes ten-minute certificates verifiable long after they expire, and it creates public accountability: anyone can see which identities signed which artefacts, so a signature made with a compromised account is discoverable rather than invisible.
It is free, widely used in production, and run by the Open Source Security Foundation with a published service level. The considerations are dependency and disclosure: your builds rely on services you do not operate, and signing events become public, which reveals repository and workflow names. Organisations uncomfortable with either can run private Fulcio and Rekor instances or sign with conventional keys held in a KMS.
For open-source distribution, container images, and language package ecosystems it largely has. Platform signing requirements, such as those for Windows executables, Apple software, or Android applications, still use the vendor’s own certificate infrastructure and are not affected. Many organisations end up with both: Sigstore for internal artefacts and ecosystem publishing, vendor certificates where a platform demands them.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.