Registry

Musher bundles are distributed as OCI artifacts via bundles.musher.dev. The registry implements the OCI Distribution Spec, so any OCI-compatible client can pull and push bundles.

Authentication

Publishing and pulling private bundles require authentication. Public bundles can be pulled without credentials. Use your Musher API key or access token to log in when needed.

musher login

echo $MUSHER_API_KEY | docker login bundles.musher.dev -u musher --password-stdin

echo $MUSHER_API_KEY | oras login bundles.musher.dev -u musher --password-stdin

Pulling bundles

Pull a bundle by specifying the namespace, bundle name, and an optional tag. If you omit the tag, latest is used.

musher load acme/code-review:1.0.0

docker pull bundles.musher.dev/acme/code-review:1.0.0

oras pull bundles.musher.dev/acme/code-review:1.0.0

Pushing bundles

Publishing bundles requires the musher CLI and write access to the target namespace. Your organization's namespace is determined during onboarding.

musher bundle push acme/code-review:1.0.0

Listing versions

View detailed information about a bundle, including available versions:

musher hub info acme/code-review

Public vs private bundles

Bundle visibility is configured per bundle in the Console.

• Public — anyone can pull the bundle without authentication. Public bundles are discoverable on the Hub. See Discovery & the Hub for details.
• Private — only members of your organization can pull the bundle. Private bundles do not appear on the Hub.