Bare names
Names such as button and dialog point to official shadcn items under the current CLI rules.
Free registry relationship mapper
Shadcn Dependency Graph
Visualize registryDependencies and npm packages in a public shadcn registry. Find circular dependencies, roots, and external references for free.
Before an install breaks
Read the relationships hidden inside registry JSON
Maintained by Diwan SachiduTechnical review:
A registry item can pull in UI primitives, blocks from another registry, and several npm packages. Those declarations are easy to skim past in a large catalog. The Shadcn Dependency Graph turns them into nodes and directed edges, then counts roots and checks local relationships for cycles.
The first view keeps npm packages hidden so the registry structure remains readable. Turn them on when you need to audit package weight or see which items share the same runtime dependency.
How dependency addresses are interpreted
Namespaced items
Addresses such as @acme/data-table remain external nodes tied to the configured namespace.
GitHub and URL items
GitHub item addresses and full URLs stay identifiable in the report. Same-origin item URLs can resolve to local catalog items.
npm packages
Package versions are combined under the package name, while each edge retains whether it came from dependencies or devDependencies.
The addressing behavior follows the current official registryDependencies documentation. External items are mapped but are not recursively downloaded by this page.
How to map a shadcn registry
- Step 1
Open the deployed catalog
Use the public registry.json response your users or the CLI can reach, rather than a local source file.
- Step 2
Build the graph
Paste the URL and map the declared registry, npm, and development dependencies.
- Step 3
Inspect roots and cycles
Root items are not referenced by another local item. Circular local groups are listed below the canvas.
- Step 4
Export before refactoring
Download the JSON report when you need a review artifact or a baseline for dependency cleanup.
Scope, safety, and limits
The server checks each hostname and redirect before fetching the catalog. Private IP ranges, local hosts, embedded credentials, responses above 2 MB, and requests longer than 10 seconds are rejected. Registry source files are never executed.
Cycle detection only covers local items that can be resolved from the submitted response. Include files, dynamic-search pages, and dependencies hosted by other registries are not fetched. For installation behavior, confirm important paths with the official CLI and a test project.
Related references: registry API and namespace resolution.
Shadcn Search is independent and is not affiliated with or endorsed by shadcn/ui.
Frequently asked questions
Check the catalog before mapping it
The Shadcn Registry Validator reports field-level schema, metadata, dependency, and file declaration problems.
Open the Shadcn Registry Validator