ns-ui / status
What is actually working.
Four questions, answered from measurements rather than from a heartbeat. Every failure this registry has had returned HTTP 200, so there is no uptime figure here, no incident log and no green banner — nothing on this page is stored over time, and anything that cannot be measured says so.
Can I install a component right now?
Yes — all 298 install payloads parse and carry real file contents, and the live registry index serves the same 298 components.
Can my agent read the registry?
Yes — llms.txt, llms-full.txt and the MCP snapshot each describe all 298 components in this build.
Can I see a component move before I install it?
No — not one of the 36 featured cards has a preview video that resolves, so every one of them silently falls back to a still poster and never moves.
Can I sign in and save components?
Not measured — one public, unauthenticated Convex query answers, which proves the backend can be read and nothing more; sign-in, saving and every authenticated path are unproven here.
Measured from this build
2026-08-04 19:39 UTC
Failed
featured previews
every featured card silently falls back to its poster
0 / 36
Drift
published tooling coverage
266 components in the published CLI package vs 298 in this build · 2026-08-04 20:39 UTC
266 / 298
Drift
screenshot gate
32 newest components are not yet gated by scripts/verify.ts
266 / 298
Fine
install payloads
every payload parses and carries non-empty file contents
298 / 298
Fine
rename redirects
every renamed slug still resolves to a component that exists
222 pairs · 888 entries · 0 broken
Fine
meta.json completeness
every component declares all seven fields verify.ts requires
298 / 298
Fine
featured posters
every featured card has both posters
72 / 72
Read live
2026-08-04 20:39 UTC
Fine
live origin
fetched from /r/registry.json, revalidated hourly
298 items
Fine
convex read path
public unauthenticated query only; auth, mutations and account surfaces are unproven by this check
reachable
Fine
published packages
npm dist-tags latest; matches this repo's package.json
cli 0.3.0 · mcp 0.2.0
Not measured, and why
Not measured
uptime and availability history
no time-series store exists in this repo
—
Not measured
incident history and error rates
no analytics or error reporting is wired here
—
Not measured
response-time percentiles
one request from one machine is not a measurement
—
Not measured
whether `npx shadcn add` succeeds in a terminal
only the payload is checked
—
Not measured
whether the ungated components render
scripts/verify.ts needs a running server
—
Not measured
Vercel deployment state
no code path in this repo reads a Vercel token
—
Build measurements were taken at 2026-08-04 19:39 UTC by scripts/build-status.ts and ship with this deployment. Live reads come from https://design.helpmarq.com/r/registry.json, the npm dist-tags for @nikolas.sapa/ns-ui and @nikolas.sapa/ns-ui-mcp, and one public Convex query, refreshed hourly.