Share feedback
Answers are generated based on the documentation.

sbx kit provenance

DescriptionShow the SLSA provenance attached to a kit
Usagesbx kit provenance REFERENCE [flags]

Experimental

This command is experimental.

Experimental features are intended for testing and feedback as their functionality or design may change between releases without warning or can be removed entirely in a future release.

Description

Print the SLSA provenance attestation attached to an OCI kit.

Provenance is attached by sbx kit push as an OCI referrer of the kit manifest. It records the kit's content digests, the sandbox image its spec declares, and the source git commit the kit was pushed from.

Provenance pushed without --sign is unsigned: it is printed but marked UNSIGNED, because anyone with push access to the repository could have written it. To verify a signed attestation, pass --key for a key-based signature, or --certificate-identity (or --certificate-identity-regexp) together with --certificate-oidc-issuer (or its regexp form) for a keyless one; only attestations that verify and whose subject matches the kit's own digest are reported as VERIFIED.

Options

OptionDefaultDescription
--certificate-identityExact keyless signer identity (certificate SAN)
--certificate-identity-regexpKeyless signer identity regexp (certificate SAN)
--certificate-oidc-issuerExact keyless OIDC issuer
--certificate-oidc-issuer-regexpKeyless OIDC issuer regexp
--insecure-ignore-tlogDo not require a Rekor transparency-log entry (for private keyless signatures)
--keyPublic key for key-based verification (PEM)

Global options

OptionDefaultDescription
-D, --debugEnable debug logging

Examples

# Show provenance (unsigned attestations are printed as-is)
sbx kit provenance ghcr.io/org/my-kit:1.0

# Verify a signed attestation before printing it
sbx kit provenance \
--certificate-identity user@example.com \
--certificate-oidc-issuer https://accounts.google.com \
ghcr.io/org/my-kit:1.0