Discofork
Repository brief

shadcn-ui/ui

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T22:14:42.651Z
3mo ago

shadcn-ui/ui

shadcn-ui/ui is a large, actively maintained open-source component library and code distribution platform for building customizable UI with multiple frameworks. It is highly popular, with 110,990 stars and 8,356 forks, and it was updated today. Forks are most interesting if you care about React/TypeScript UI tooling, registry/distribution workflows, or customizing a well-known component system rather than starting from scratch.

GitHub
Loading tags...
Stars110,990
Forks8,356
Default branchmain
Last pushed2026-03-29T08:04:20Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Prefer this fork only if you want an older, near-vanilla baseline and plan to maintain it yourself. If you want current shadcn/ui behavior, upstream is the better choice.

Choose this fork only if you want Kodkafa-specific branding and workflow changes and do not need to stay close to upstream. For most adopters, upstream shadcn-ui/ui is the safer choice because this fork is heavily behind and appears to remove or replace substantial upstream registry/example content.

Choose this fork only if you need its older registry/CLI behavior and are prepared to own the drift. If you want current shadcn/ui components, examples, and maintenance, upstream is the better default.

Choose this fork only if its added framework and registry workflows match your needs. If you want the safest path for a general-purpose shadcn/ui install, upstream is a better default because this fork is materially behind and appears to have removed or replaced a lot of upstream content.

Choose this fork if your goal is to launch or customize a shadcn registry quickly. Choose upstream if you want the latest full component platform, broader framework support, and less divergence risk.

Prefer the upstream project unless you specifically need this older snapshot. This fork offers no visible extra capability, while upstream has continued active maintenance and feature work.