Component inventories
A component inventory lists the software in one runner image or plugin and is bound to that artifact’s immutable sha256 digest. Waza publishes one for every reference runner image, can bind it into a provenance bundle, and verifies offline that an inventory describes exactly the image or plugin you consumed.
Format
Section titled “Format”CycloneDX 1.6 JSON (application/vnd.cyclonedx+json) restricted to the closed
profile waza.component-inventory/1.0
(schema):
metadata.componentis the subject:container(image) orapplication(plugin), oneSHA-256hash equal to the subject digest, andbom-refimage:sha256:<hex>orplugin:sha256:<hex>.componentslists each component once, sorted bybom-ref(the package URL when one exists). At most 20,000 components and 16 MiB.
Generation is deterministic; the required serialNumber is a version 5
urn:uuid derived from the inventory content.
Verify a published reference image offline
Section titled “Verify a published reference image offline”digest=sha256:<hex>gh attestation verify "oci://ghcr.io/microsoft/waza-runner-reference@$digest" \ --repo microsoft/waza --predicate-type https://cyclonedx.org/bom \ --signer-workflow microsoft/waza/.github/workflows/publish-runner-reference.yml \ --format json | jq '.[0].verificationResult.statement.predicate' > runner.cdx.jsonwaza runner inventory verify --inventory runner.cdx.json \ --image-digest "$digest" --image-reference ghcr.io/microsoft/waza-runner-referenceThe tag-release publisher generates the inventory from the pushed digest, verifies it, and attests it to that digest; the public-digest verifier rejects a digest without a verified inventory. Candidate qualification stores the runner image archive and digest-bound inventory only in workflow-run artifacts; it does not push an image or create a registry tag. See the candidate qualification procedure.
Verify a plugin offline
Section titled “Verify a plugin offline”waza runner inventory verify --inventory example-plugin.cdx.json \ --plugin example-plugin.tgz --plugin-name example-plugin--plugin hashes the artifact you are about to load. The runner does not load
plugins today; deployments that add plugin artifacts must ship an inventory
generated with --subject plugin and verify it before loading.
Generate
Section titled “Generate”waza runner inventory generate --name ghcr.io/org/waza-runner --digest sha256:<hex> \ --go-binary ./waza --embedded-dir internal/embedded --dpkg-status ./dpkg-status \ --os-release ./os-release --out runner.cdx.jsonwaza runner inventory generate --subject plugin --name example-plugin \ --subject-file example-plugin.tgz --from-cyclonedx deps.cdx.json --out plugin.cdx.jsonSources: --go-binary (Go build information and file digest), --embedded-dir
(bundled Copilot CLI and runtime payloads proven present in the binary), --dpkg-status,
--os-release, --file and --from-cyclonedx. Generation refuses tags,
never overwrites --out, and fails on conflicting definitions of one component.
Bind into provenance
Section titled “Bind into provenance”waza runner provenance generate ... --image-digest sha256:<hex> \ --bind component-inventory=runner.cdx.jsonwaza runner provenance verify --bundle bundle --public-key signing.pub.pem --require-inventoryThe binding verifier checks the inventory’s subject against the signed runner image digest and repository; generation refuses to sign a mismatched inventory.
Report and failure codes
Section titled “Report and failure codes”verify prints a waza.inventory-verification
report with checks inventory, profile, subject, binding and
components: exit 0 verified, 1 failed, 2 invalid flags.
| Code | Meaning |
|---|---|
inventory_missing, inventory_malformed, inventory_too_large |
No usable inventory |
profile_unsupported |
Other profile version |
subject_unbound, subject_purl_mismatch, subject_ref_mismatch, subject_kind_invalid |
Subject not bound to one digest, or altered |
expected_digest_missing, expected_digest_invalid |
No consumed digest, or a tag |
subject_digest_mismatch, subject_kind_mismatch, subject_name_mismatch |
Inventory is for another image or plugin |
expected_name_invalid |
The pinned name exceeds 512 characters |
expected_kind_invalid |
The requested kind is neither image nor plugin |
components_empty, component_duplicate, component_ref_mismatch, component_purl_mismatch |
Component list altered or internally contradictory |
binding_required_missing |
--require-inventory and the bundle binds none |
The inventory’s integrity comes from the signature that delivered it (the GHCR attestation or the provenance bundle). The Lab runner page includes a Component inventory panel for the same check; see Dashboard Lab.
Migration
Section titled “Migration”Additive. Images published before v0.42.0 have no inventory attestation until
republished; provenance bundles need an inventory only when the verifier passes
--require-inventory.