---
layout: doc
title: Introducing the Kubb registry
description: The Kubb registry lists reviewed plugins, adapters, and parsers. kubb add installs one and adds it to your config, and kubb update keeps it current.
outline: deep
image: /blog/kubb-registry/cover.svg
date: 2026-10-13
---

> Index of every page on this site: [llms.txt](https://kubb.dev/llms.txt)

![Introducing the Kubb registry](/blog/kubb-registry/cover.svg)

# Introducing the Kubb registry

Adding a plugin used to take three steps: find the package, install it, and add it to `kubb.config.ts`. Now one command does all three:

```shell [Terminal]
kubb add plugin-zod
```

The command reads the [Kubb registry](/docs/5.x/reference/registry), a reviewed list of plugins, adapters, and parsers.

## One reviewed version per extension

The registry lives in [kubb-labs/registry](https://github.com/kubb-labs/registry). Each record pins one version of an extension: an npm version, or the commit of a GitHub release. A maintainer reviews every version before `kubb add` installs it, so a new release reaches your project only after someone has looked at it.

You can browse the registry at [kubb.dev/extensions](/extensions). Each page shows the docs the package ships: an overview, its options, and how-to guides. Kubb Studio reads the same registry.

## Add an extension

[`kubb add`](/docs/5.x/reference/commands/add) takes a registry id. Official extensions use their short name, such as `plugin-zod`. Community extensions use `<owner>/<slug>`, such as `acme/plugin-graphql`.

Then `kubb add`:

1. Checks that it supports your Kubb and Node.js versions.
2. Installs the pinned version as a dev dependency, with the package manager your project uses: npm, pnpm, Yarn, or Bun.
3. Adds the plugin's import and call to `kubb.config.ts`. For an adapter or parser, it prints the code to add.

## Keep extensions current

[`kubb list`](/docs/5.x/reference/commands/list) shows what you have installed and what the registry pins:

```text [Output]
ID                    PACKAGE           INSTALLED  REGISTRY  UPDATE
kubb-labs/plugin-ts   @kubb/plugin-ts   5.4.2      5.4.4     yes
kubb-labs/plugin-zod  @kubb/plugin-zod  5.4.4      5.4.4     no
```

[`kubb update`](/docs/5.x/reference/commands/update) installs the pinned versions. Pass `--check` to only list them. It never downgrades a package.

Every Monday, a workflow opens a pull request that moves each pin to the latest release. Once a maintainer merges it, your next `kubb update` installs the new versions.

## List your own extension

Ship a [`kubb-extension.json`](/docs/5.x/reference/kit/manifest) and a [`docs/` folder](/docs/5.x/reference/kit/extension-docs) with your package. Publish it to npm, or tag a GitHub release. Then open a submission issue. [Submit to the registry](/docs/5.x/how-to/submit-to-the-registry) walks through each step.

## Try it

`kubb add`, `kubb list`, and `kubb update` ship with Kubb 5.8.1. Update to 5.8.4 or later to also install extensions pinned to a GitHub release. To run your own registry, see [Host your own registry](/docs/5.x/reference/registry#host-your-own-registry).

Feedback goes to [GitHub](https://github.com/kubb-labs/kubb/issues) or [Discord](https://discord.gg/shfBFeczrm).

## Sitemap

See the full [sitemap](https://kubb.dev/sitemap.md) for all pages.