Build provenance is increasingly required
Frameworks like SLSA and compliance standards are moving toward requiring verifiable build provenance. Evidence packages create the records these standards expect.
CI Evidence Pack generates structured evidence packages from CI/CD pipeline runs. Each package captures build metadata, artifact hashes, environment details, and provenance records in a tamper-evident format that can be verified, stored, or attached to release artifacts.
Why it matters
Frameworks like SLSA and compliance standards are moving toward requiring verifiable build provenance. Evidence packages create the records these standards expect.
Knowing that a release artifact was built from a specific commit, on a specific runner, at a specific time, and being able to prove it, is a baseline requirement for supply chain trust.
Manually documenting build details is error-prone and unreliable. CI Evidence Pack generates the evidence automatically as part of the pipeline, not as an afterthought.
CI Evidence Pack runs as a CLI command in any pipeline that supports shell execution: GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure DevOps, and others.
Built with
FAQ
Built by Orygn
Orygn builds custom software, security tooling, and infrastructure-level systems. CI Evidence Pack is a working example of that approach applied to build provenance and supply chain integrity.
View on GitHub