OPERATING DOCUMENT / OPENFORGE

Release Security

Cryptographic signing, SBOM generation, provenance attestations, and distribution trust.

01 / Context02 / Procedure03 / Operations04 / Verification

Release Security

Release artifacts must provide cryptographic proof of authenticity and tamper-resistance.

Requirements

  • Digital Signatures: Binaries and container images signed with verifiable public keys.
  • SBOM Inclusion: SPDX or CycloneDX SBOM manifests published alongside releases.
  • Build Provenance: Verifiable SLSA build attestations proving generation in secure CI pipelines.

Canonical Source

DOCUMENT TRACE

Return to the project record to see architecture, development pulse, proof and related field notes in one context.