Sources
Every item in every public shadcn registry, re-crawled and re-counted every night.
Every figure BlockDex states about the world, rather than about itself, is listed here. Each one names the page it was read from and the day it was read. Nothing on this site retypes a number: a page renders a figure by asking this register for it, and asking for a claim that is not marked verified throws rather than printing something.
5 claims · 3 sources · 0 of 5 re-checked automatically
registry.json
A shadcn registry publishes its manifest as registry.json at the root of the registry endpoint
shadcn/ui — Registry: Getting Started. Read 2 August 2026. Not yet re-checked automatically — this one is confirmed by reading it.
/r/[NAME].json
Individual registry items are served at /r/[NAME].json
The crawler's whole free/paid test is 'ask the item endpoint for the source'. If the endpoint shape moves, the method page stops describing what the crawler does.
shadcn/ui — Registry: Getting Started. Read 2 August 2026. Not yet re-checked automatically — this one is confirmed by reading it.
shadcn@latest add <REGISTRY_ITEM_URL>
The shadcn CLI installs a component from any third-party registry by URL — shadcn@latest add <item URL>
This is the sentence that makes the index useful — one CLI installs from all 810 indexed registries. It is repeated in four places, so it drifts in four places.
shadcn/ui — Registry: Getting Started. Read 2 August 2026. Not yet re-checked automatically — this one is confirmed by reading it.
277
shadcn publishes an official registry directory, and it lists 277 registries
shadcn/ui — official registry directory. Read 13 August 2026. Not yet re-checked automatically — this one 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
shadcn/ui — Registry: Dynamic Search. Read 13 August 2026. Not yet re-checked automatically — this one is confirmed by reading it.
BlockDex is built and run by Kynth Studios. 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, because either one is a supported way to record that a claim stopped being true and publish it anyway. 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 instead of guessing.
