Documentation
¶
Overview ¶
Command openvex-bind projects the committed OpenVEX document onto one platform manifest digest, producing the document the release publishes as a `--type openvex` Cosign attestation on that manifest (NVIDIA/aicr#2426).
Why a projection and not a committed file: verification requires the VEX product identifier to bind to the specific manifest the claim covers, and that digest does not exist until the image is built. `.openvex.json` stays the reviewed source of truth with bare `pkg:oci/<name>` products; this tool rewrites those to `pkg:oci/<name>@sha256:<platform-manifest-digest>` and writes the result to a file the attest step feeds to `cosign attest`. The source document is never modified.
What it does not do: no format translation, no status or justification mapping, no merging of scan results. Statuses, justifications, impact statements and subcomponents pass through untouched, because the curated judgment is exactly what has value and any rewrite of it is a guess.
Output is deterministic — a pure function of the source bytes, the image name and the digest, with no wall clock and no UUID — so a re-run of a release produces byte-identical evidence.
Usage:
openvex-bind -in .openvex.json -out vex-linux-amd64.openvex.json \ -image ghcr.io/nvidia/aicr-validators/aiperf-bench \ -digest sha256:<64 hex>
Source Files