systems
Component registry
A shareable, installable collection of components that any team can publish and any developer can pull from via CLI – shadcn's Registry 2.0 generalisation of copy-owned code.
The code-ownership model extended from “copy this one component” to “publish and pull whole collections”: since 2025, any team – or any public GitHub repo carrying a registry.json file – can publish a registry, and any developer can install from it with the same CLI that installs shadcn’s own components.
The shift this represents: component distribution stops being something only library vendors do, and becomes something any team does with its own patterns – an internal design system’s components can be pulled into a new project the same way public ones are, still arriving as owned, editable source rather than a locked dependency.