Current shadcn schema
Parses the response with the registry schema exported by the installed shadcn package.
Free registry health check
Shadcn Registry Validator
Use the free Shadcn Registry Validator to check a public registry.json URL for schema errors, duplicate names, dependencies, unsafe paths, and MCP readiness.
Before you publish
Check the registry your users actually receive
Maintained by Diwan SachiduTechnical review:
A source registry can look correct in a repository while its deployed endpoint is stale, malformed, or missing important metadata. The Shadcn Registry Validator reads the public catalog URL, parses the response with the current shadcn schema, and turns the result into a short repair list.
The extra checks focus on mistakes that are easy to overlook during authoring: duplicate names, repeated dependencies, self-references, thin descriptions, duplicate file paths, and targets containing parent-directory segments. The result is a spot check of one response, not a review of the component source code.
What the registry checker inspects
Names and metadata
Checks item names, duplicate entries, homepage metadata, schema references, and useful descriptions.
Dependencies
Finds repeated npm or registry dependencies and direct self-references that can break resolution.
File declarations
Looks for duplicate paths and parent-directory segments in declared files and targets.
How this validator works
The validator checks the deployed JSON returned by the URL you enter. It does not inspect your repository, run generated code, or install registry items.
- Fetch safety
- Each hostname and redirect is checked before download. Local hosts, private network addresses, and URLs containing credentials are rejected. Requests allow up to three redirects, wait no longer than 10 seconds, and stop at 2 MB.
- Schema validation
- The response is parsed as JSON and checked with the registry schema exported by the installed shadcn 4.19.0 package. Schema errors are reported with their field paths when available.
- Registry hygiene
- A second pass looks for duplicate names and file paths, repeated or self-referencing dependencies, unsafe parent paths, missing metadata, weak descriptions, and duplicate include entries.
- One-request report
- The API returns the report for the submitted request with no-store cache headers. This route does not write the registry payload or report to application storage.
How the score is calculated
Every report starts at 100. Each error removes 12 points and each warning removes 3, with a minimum score of zero. Scores of 90 or higher are marked healthy, scores from 70 to 89 need attention, and lower scores are critical. This is a snapshot from this validator, not the official shadcn Registry Health score.
Technical references: registry.json, registry API, Registry Health, and registry authentication.
Shadcn Search is an independent project and is not affiliated with or endorsed by shadcn/ui.
How to validate a registry.json file
- Step 1
Publish the registry catalog
Deploy the registry and copy the public JSON catalog URL. A browser request to that address should return JSON without a login.
- Step 2
Run the registry check
Paste the URL above and choose Analyze registry. The report separates schema failures from maintainability warnings.
- Step 3
Fix errors before warnings
Schema errors and unsafe or duplicate file declarations deserve attention first. Then improve names, descriptions, and dependency lists.
- Step 4
Confirm with the CLI
Validate the source registry locally and dry-run a few representative installs before publishing the final update.
For the local check, run npx shadcn@latest registry validate ./registry.json. The browser report and CLI check answer related but different questions, so a production registry benefits from both.
Shadcn Registry Validator, the CLI, and Registry Health
Shadcn now has several validation surfaces. Choosing the right one depends on whether you are authoring a registry, checking a deployed catalog, or monitoring a directory listing.
| Option | Best for | Scope |
|---|---|---|
| Shadcn Registry Validator | A quick check of one deployed public catalog | Current response, schema, metadata, dependencies, and file declarations |
| shadcn CLI | Local development, GitHub sources, and CI | Source registries, includes, item files, and command-line diagnostics |
| Official Registry Health | Registries listed in the shadcn directory | Repeated availability, schema, sampled item, and CLI observations over time |
The official Registry Health documentation describes its directory monitoring as experimental. Its score is based on observations over time; the score above belongs only to the URL and moment you tested.
Limits and privacy
Shadcn Registry Validator fetches the public URL you submit and permitted redirects. It blocks localhost and private network destinations, limits response size and request time, and does not send registry authentication headers. Private registries are intentionally out of scope.
Included registry files and referenced item URLs are not fetched recursively in this release. A clean report also does not prove that every item installs or compiles. Run CLI validation, dry-run representative installs, and test the generated files in CI before a release.
Frequently Asked Questions
Turn a live site into design context
Use the DESIGN.md Generator to extract observed colors, typography, spacing, and interface patterns from a public webpage.
Open the DESIGN.md Generator