Every item in every public shadcn registry, re-crawled and re-counted every night.
registry.json
A shadcn registry publishes its manifest as registry.json at the root of the registry endpoint
Source: shadcn/ui — Registry: Getting Started. Read 2 August 2026. A job re-fetches this page and looks for the wording the figure came from. It last found it 14 September 2026.
/r/[NAME].json
Individual registry items are served at /r/[NAME].json
Source: shadcn/ui — Registry: Getting Started. Read 2 August 2026. A job re-fetches this page and looks for the wording the figure came from. It last found it 14 September 2026.
shadcn@latest add <REGISTRY_ITEM_URL>
The shadcn CLI installs a component from any third-party registry by URL — shadcn@latest add <item URL>
Source: shadcn/ui — Registry: Getting Started. Read 2 August 2026. A job re-fetches this page and looks for the wording the figure came from. It last found it 14 September 2026.
344
shadcn publishes an official registry directory, and it lists 344 registries
Source: shadcn/ui — official registry directory. Read 13 September 2026. No job re-checks this one yet. It is confirmed by reading it.
shadcn search
The shadcn CLI can search inside a registry the user has configured — `shadcn search` — so "nobody indexes what is inside a registry" is false and must never be claimed again
Source: shadcn/ui — Registry: Dynamic Search. Read 13 August 2026. A job re-fetches this page and looks for the wording the figure came from. It last found it 14 September 2026.
How this register works
BlockDex is built and run by Compound Labs. This register is a file in this product's repository and the re-check is a build gate. There is no flag to skip it and no list of known exceptions. Where a source could not be read at all, the claim is kept with no value and the page it would have appeared on says so.