Repository navigation
v1.2.0: signed SBOMs
SBOMs can now carry a Sigstore signature, which Exposa verifies on upload and shows as signed when one of your organization's trusted publishers made it (Exposa ADR 0007).
New
sign: true: signs each SBOM keyless with cosign and uploads the signature with it. Needssigstore/cosign-installerandpermissions: id-token: write.- Signature files next to the SBOM: a
<file>.sigstore.jsonis uploaded as that SBOM's signature, and*.sigstore.jsonfiles are never uploaded as SBOMs. - SBOM attestations: save the bundle from
actions/attest-sbomas<file>.sigstore.json. Exposa verifies it and records which files (e.g. firmware images) the SBOM describes. Needs an Exposa version with attestation support; public repositories only for now. - The job summary has a Signature column (
verified,untrusted,unsigned).
Behavior
- A signature by a repository your organization doesn't trust is stored as "signed, untrusted", with a warning.
- The step fails on a signature that doesn't verify (400), when the organization requires signed SBOMs and the upload has none (403), and retries when Exposa can't check signatures right now (503).
Without sign and without .sigstore.json files, uploads work as in v1.1.0.
See the README.