Registry schema

The Mzizi registry follows the shadcn registry schema.

The manifest

registry.json at the repository root is the single source of truth for every registry item:

{
  "$schema": "https://ui.shadcn.com/schema/registry.json",
  "name": "mzizi",
  "homepage": "https://mzizi.dev",
  "items": []
}

Field	Type	Description
`$schema`	string	Schema URL for validation
`name`	string	Registry identifier — `mzizi`
`homepage`	string	Registry homepage
`items`	array	The registry items

An item

{
  "name": "button",
  "type": "registry:ui",
  "description": "Displays a button or a component that looks like a button.",
  "dependencies": ["radix-ui", "class-variance-authority"],
  "registryDependencies": [],
  "files": [
    {
      "path": "components/registry/n2-primitives/button.tsx",
      "type": "registry:ui"
    }
  ]
}

Field	Type	Required	Description
`name`	string	Yes	Unique kebab-case identifier
`type`	string	Yes	Item type — see below
`description`	string	Yes	Human-readable description
`dependencies`	string[]	Yes	npm package names
`registryDependencies`	string[]	Yes	Other registry item names
`files`	object[]	Yes	The files composing the item

The file object

Field	Type	Description
`path`	string	Path from the repository root
`type`	string	File type, matching the parent item type
`content`	string	Source — populated by the API, not stored in the manifest

Item types

Counts read from GET https://api.mzizi.dev/v1/ui on 29 September 2026. They move; read the endpoint rather than this table.

Type	Count	Installs to	What it is
`registry:ui`	420	`components/ui/`	React components (the React build) — CVA variants, Radix primitives, `cn()` composition
`registry:block`	105	composed sections	Higher-level compositions of several components
`registry:lib`	47	`lib/`	Pure functions, patterns and infrastructure — `utils`, `observability`, `circuit-breaker`, `retry`, `timeout`, `fallback-chain`, `chaos`, `ai-safety`
`registry:hook`	3	`hooks/`	`use-toast`, `use-mobile`, `use-memory-pressure`
`registry:base`	1	the base layer
`registry:theme`	1	the theme

API response format

GET /v1/ui/{name} returns the manifest entry enriched with inlined source:

{
  "name": "button",
  "type": "registry:ui",
  "description": "Displays a button or a component that looks like a button.",
  "dependencies": ["radix-ui", "class-variance-authority"],
  "registryDependencies": [],
  "files": [
    {
      "path": "components/registry/n2-primitives/button.tsx",
      "type": "registry:ui",
      "content": "\"use client\"\n\nimport * as React from \"react\"\n..."
    }
  ]
}

content carries the complete, installable source.

The index

GET /v1/ui returns every item without source:

{
  "$schema": "https://ui.shadcn.com/schema/registry.json",
  "name": "mzizi",
  "homepage": "https://mzizi.dev",
  "items": [
    { "name": "accordion", "type": "registry:ui", "description": "..." },
    { "name": "alert", "type": "registry:ui", "description": "..." }
  ]
}

The registry’s name is mzizi. An earlier version of this document said mukoko; the manifest is the authority and it does not.

No static build output

The registry does not write one JSON file per item. There is no pnpm registry:build and no public/r/: the registry has had no public/ since it removed its app on 2 October 2026. Each item is served by the API instead: GET https://api.mzizi.dev/v1/ui/<name> returns the shape above, inlined source included, from the registry’s files at the API’s pinned commit.

Mzizi Roots

The registry

Registry architecture

Foundations

Patterns

Blocks

Charts

Content style

Registry schema

The manifest

An item

The file object

Item types

API response format

The index

No static build output

​The manifest

​An item

​The file object

​Item types

​API response format

​The index

​No static build output

The manifest

An item

The file object

Item types

API response format

The index

No static build output