repowiserepowise

Library

shadcn-ui / ui

Composable, accessible components with thoughtful defaults. Build your own component library with code you can customize, extend, and make your own.

★ 128,469stars on GitHubTypeScriptMITCurated

Claude Code, Cursor, Codex or VS Code. No key. You approve one sign-in in your browser.

Setup instructions on GitHub

Releases on GitHub (latest shadcn@4.23.0, Oct 27, 2026)

Repowise maps public repos from their source. Not affiliated with shadcn-ui. What is Repowise?

github.com/shadcn-ui/uiIndexed at 968d8cbRefreshes weekly

What is ui?

shadcn/ui is a set of components that developers customize, extend, and build on to make their own component library. Its core idea is that the component code is yours to change, so the library is built from code you control. The project is written mainly in TypeScript and is licensed under MIT. Its code health is 9.3 out of 10 (Excellent), ranked #9 of 4,000+ indexed repos. The last commit to ui was on Nov 2, 2026, and 648 people have contributed.

As of commit 968d8cb, indexed Nov 18, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.

For agentsui.md

Repo facts: type, license, health, rank, contributors
ui facts
TypeLibrary
LicenseMIT
Code health9.3 / 10 (Excellent)
Health rank#9 of 4,000+ indexed repos
Last commitNov 2, 2026
Contributors648
Bus factor1
Size5,449 files, 487,927 lines

Explore ui

Ask about this code in your agent

This connects Repowise to ui's code. It does not install ui.

Useful if you want to change or fork ui: your agent can ask how it is put together and get answers that cite its files.

Ask about ui

Answers come from ui's README and source, with the files they cite. Two free answers a day without an account.

Featured answer

The ui repository (shadcn-ui/ui) is a set of composable, accessible components that developers customize, extend, and build on to make their own component library, written mainly in TypeScript and licensed under MIT. Its core idea is that the component code is yours to change, so the library is built from code you control. The command-line tool lives in packages/shadcn, with its entry point at packages/shadcn/src/index.ts, and the init command in packages/shadcn/src/commands/init.ts is one of the hotspot files. The shared registry logic is in packages/registry, whose entry point packages/registry/src/registry/index.ts exposes the registry code, and updater modules such as packages/registry/src/updaters/update-files.ts handle changes to project files. The apps/v4 directory holds the documentation site and the component registry its examples draw from, and the templates directory provides starter code for several app stacks. To start reading, begin with the CLI entry point and then the registry; the layer chart shows 5449 files in total, with 1716 in Application, 713 in UI, and 2693 in Docs & Tooling.

Files per layer in ui8 layers.

Basis: Inferred · knowledge graph· as of 968d8cb

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of shadcn-ui/ui from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

shadcn-ui/ui FAQ

What is shadcn/ui?

shadcn/ui is a set of components that you can customize, extend, and build on to make your own component library. It is open source and licensed under MIT. The components are meant to be changed rather than used only as fixed packages.

How does shadcn/ui work?

shadcn/ui provides component code that you customize and extend in your own project. Its repository includes a command-line tool in packages/shadcn and shared registry logic in packages/registry. Starter code for several app stacks is kept in the templates directory.

What language is shadcn/ui written in?

shadcn/ui is written mainly in TypeScript. The repository also contains JavaScript, Astro, Dockerfile and shell files.

How is the shadcn/ui code organized?

The apps/v4 directory holds the documentation site and its component registry. The packages directory holds the command-line tool and registry libraries, and the templates directory holds starter apps for several stacks.

Who is shadcn/ui for?

shadcn/ui is for developers who want to build their own component library from components they can customize. The project states that it is meant to be used to build your own component library.

What license does shadcn/ui use?

shadcn/ui uses the MIT license, whose SPDX identifier is MIT. The license applies to the open source code in the repository.

Code health

9.3out of 10Excellent

Hotspots average 7.9, the place fixes pay off most.

On the leaderboards:#2 of 70 TypeScript repos

Key features of ui

  • Provides a set of designed components that you can customize, extend, and build on.
  • Lets you start from the provided components and then make them your own.
  • Is open source, with the code available for you to read and change.
  • Is intended for building your own component library.
  • Includes a command-line tool and shared registry logic for working with component code.

How shadcn-ui/ui works

The command-line tool lives in packages/shadcn, and its entry point is packages/shadcn/src/index.ts. The init command in packages/shadcn/src/commands/init.ts is one of the hotspot files in the repository. The shared registry logic is in packages/registry, and its entry point packages/registry/src/registry/index.ts exposes the registry code. Updater modules such as packages/registry/src/updaters/update-files.ts handle changes to project files. The apps/v4 directory holds the documentation site and the component registry its examples draw from. The templates directory contains starter code for several app stacks, such as templates/astro-app/src/layouts/main.astro for an Astro app.

The codebase has 5,449 files and 12,290 symbols in 7 modules, led by TypeScript, JavaScript and Astro. Code health is 9.3 out of 10, rated excellent.