Answers are generated based on the documentation.

sbx kit push

DescriptionPush a kit artifact to an OCI registry
Usagesbx kit push DIRECTORY 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

Package and push a kit artifact directory to an OCI registry.

The directory must contain a valid spec.yaml. The reference should be in the format "registry/repo:tag" (e.g., "ghcr.io/myorg/my-plugin:1.0").

The OCI artifact format is selected from the kit's spec.yaml: schemaVersion: "1" → legacy ZIP-based artifact schemaVersion: "2" → v2 tar+gzip layer with the spec in the manifest config blob and standard OCI annotations (so distribution tooling can read kit metadata without pulling layers)

With --sign, the pushed manifest is signed and the Sigstore bundle is attached to the kit as an OCI referrer. Signing is keyless (Fulcio + Rekor) unless --key is given for key-based signing.

Every push also attaches a SLSA provenance attestation as an OCI referrer, recording the kit's content digests, the declared sandbox image, and the source git commit when the directory is a working tree. The provenance is unsigned unless --sign is given, in which case it is signed as a DSSE in-toto attestation with the same identity or key.

Authentication uses the Docker credential store.

Options

OptionDefaultDescription
--identity-tokenOIDC identity token for keyless signing; defaults to the ambient CI provider, then an interactive browser login
--identity-token-fileFile holding the OIDC identity token; keeps it out of the process arguments
--keyPrivate key for key-based signing (PEM); omit for keyless signing
--signSign the pushed kit and attach the signature as an OCI referrer
--tlog-uploadtrueUpload the keyless signature to the Rekor transparency log; set false for private kits

Global options

OptionDefaultDescription
-D, --debugEnable debug logging