What would you like to secure?

Software from build to production

Can you trust what reaches production?

Between a build and a deployment, an artifact passes through registries, caches and many hands. Sigill seals what your pipeline produced, so whatever arrives later can be checked against it.

03 · How Sigill helps

Sigill records which workflow run asked for the evidence, from a token GitHub signs.

01 / 04

Your pipelineWorkflow run

Your GitHub Actions workflow builds as usual. The Sigill Evidence action hashes the output on the runner; only fingerprints are sent.

Built for GitHub Actions · other pipelines can use the API with a key, without the signed run identity

What the evidence proves

  • These exact bytes existed at the time of the timestamp.
  • Your organisation, or the Sigill Platform Seal, sealed them.
  • In Sigill's record: which repository, commit, workflow and run asked for the evidence, according to GitHub's signed token.

What it does not prove

  • Which workflow built the artifact, from the seal file alone. That link is kept in Sigill's record.
  • How the bytes were built. For that, add GitHub artifact attestations.
  • That the source code or its dependencies were free of flaws.