Registry
The hanzo registry commands.
Also for this capability: API · CLI · MCP · SDKs
Your container and package registry: push images, pull them back, see what you store.
hanzo registry tagsEvery command takes --json for the raw response and --help for its own flags. Sign in once with hanzo auth login; the commands below use that session, and the org they act in is the one it carries.
| Command | What it does |
|---|---|
hanzo registry images | Lists the org's container repositories, read live from the OCI catalog and filtered server-side to the org's namespace — the page can only ever hold the caller's own images. |
hanzo registry packages | Lists the org's npm packages — <org> and @<org>/… — from the npm registry's search index, optionally narrowed by a query within that scope. |
hanzo registry projects | Lists the namespaces the caller can see with what each holds: the org's slug, its repository count on the OCI catalog, and its package count on the npm registry. |
hanzo registry status | Reports whether the OCI and npm registries are reachable and, when the OCI half is auth-gated, which token realm its challenge advertises — an honest lens for "is the registry plane up", never a fabricated ok. |
hanzo registry tags | Lists one org-owned repository's tags, read live from the OCI registry. |
hanzo registry token | Mints a short-lived, pull-only registry token for exactly one of the org's images, through the same IAM realm the docker CLI authenticates against. |
Was this page useful?