shadcn/ui

Why it's ranked here

The distribution machinery is the real product. Fourteen commands cover scaffolding, install, preview, migration, registry build and validation, and an agent server publishes seven tools over the Model Context Protocol. Rewrites run through a TypeScript syntax tree with seven transformers rather than string replacement, and registry failures carry thirteen distinct error types instead of one opaque fetch failure. That is more engineering than a copy paste component gallery would need, which is the point: the catalogue is the demo, the pipeline is the tool.

What's good

You can see what will happen before anything is written. Preview mode shows resolved paths, diffs against your existing files, and CSS changes, including third party registry code you may want to audit first. Namespaced registries and repository addresses mean private component sets work exactly like the public one. Migrations exist for swapping between six icon libraries and for right to left support. MIT licensed. The workspace also enforces a minimum age on newly published dependency releases, a small supply chain hedge most repositories skip.

Tradeoffs

Owning the code means there is no upgrade channel. Updates are a manual diff and merge, per component, per project, forever. The catalogue pins one charting dependency to an exact version while a date picker floats to latest, so two installs on different days can differ. Two command references inside the repository disagree: one names a different default preset and lists a monorepo template the installation guide omits. The registry documentation says the format is not limited to React, but every shipped item is React with Tailwind, so that claim describes the format, not the catalogue.

How to use it well

Best fit: a React and Tailwind team that wants component source living in its own repository, and any team handing internal components to other teams without publishing a package. Set it up once, then make preview mode the habit for every later change so upgrades stay reviewable. If you run coding agents, the shipped skill file and agent server are the intended path. It does not give you a versioned dependency to pin, a way to push fixes to people who already installed, or any design token management outside code.

Observed

License

MIT (LICENSE.md)

Interfaces

CLI plus a Model Context Protocol server exposing seven tools

CLI surface

Fourteen subcommands registered in packages/shadcn/src/index.ts

Rewrite engine

ts-morph AST pipeline with seven default transformers

Error handling

Thirteen typed registry error classes exported from packages/shadcn/src/registry/index.ts

Repo layout

pnpm workspace over apps and packages, test and fixture trees excluded

Supply chain policy

2880 minute minimum release age in pnpm-workspace.yaml with a four package exclusion list

Project templates

next, vite, start, react-router, astro

Icon migration targets

lucide, tabler, hugeicons, phosphor, remixicon, radix

Agent packaging

Ships an agent skill file at skills/shadcn/cli.md

Catalogue format

apps/v4/registry.json declares items with npm dependencies, registry dependencies and file paths