Skip to main content

ns-ui / status

What is actually working.

The banner states the worst of the live reads taken for this page. The strips under it are drawn only from snapshots that were recorded: a day with no snapshot is grey, nothing is backfilled, and an uptime figure appears only once there is a recorded day behind it. Because every failure this registry has had returned HTTP 200, the questions further down carry the part a green strip cannot.

Fully operational

Every live read taken for this page came back clean. Read at 2026-11-02 18:47 UTC.

Registry origin

now: operationallast recorded day: operational

design.helpmarq.com

90 days100.0% · 90 days recorded since 5 Aug 2026

Convex read path

now: operationallast recorded day: operational

useful-peccary-556.convex.cloud

90 days100.0% · 90 days recorded since 5 Aug 2026

Published CLI package

now: operationallast recorded day: operational

@nikolas.sapa/ns-ui

90 days93.3% · 90 days recorded since 5 Aug 2026

This strip starts empty. Days before this package got its own check were recorded against a single combined published-packages check that read both packages together and could not tell them apart, so they are not redrawn as if this package had been measured on its own.

Published MCP package

now: operationallast recorded day: operational

@nikolas.sapa/ns-ui-mcp

90 days93.3% · 90 days recorded since 5 Aug 2026

This strip starts empty. Days before this package got its own check were recorded against a single combined published-packages check that read both packages together and could not tell them apart, so they are not redrawn as if this package had been measured on its own.

  • operational
  • degraded
  • down
  • no data

Can I install a component right now?

Yes: all 542 install payloads parse and carry real file contents, and the live registry index serves the same 542 components.

Can my agent read the registry?

Partly: llms.txt describes 546 of 542 components and llms-full.txt describes 546 of 542 components, so an agent reading it is working from an incomplete registry.

Can I see a component move before I install it?

Yes: every featured card has both its preview videos and both its posters (41 / 41 cards, 82 / 82 poster files).

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-10-21 10:13 UTC

Fine

featured previews

every featured card has both preview videos

41 / 41

Fine

published tooling coverage

the published CLI package indexes every component in this build · 2026-11-02 18:47 UTC

542 / 542

Fine

screenshot gate

every component carries the light and dark screenshots verify.ts gates on

542 / 542

Fine

install payloads

every payload parses and carries non-empty file contents

542 / 542

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

542 / 542

Fine

featured posters

every featured card has both posters

82 / 82

Read live

2026-11-02 18:47 UTC

Fine

live origin

fetched from /r/registry.json, revalidated hourly

542 items

Fine

convex read path

public unauthenticated query only; auth, mutations and account surfaces are unproven by this check

reachable

Fine

published CLI package

npm dist-tags latest matches this repo's package.json, and the data/registry-index.json it ships indexes every component in this build

0.11.0 · 542 components

Fine

published MCP package

npm dist-tags latest matches this repo's package.json, and the data/registry-snapshot.json it ships indexes every component in this build

0.10.0 · 542 components

Not measured, and why

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-10-21 10:13 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-tag and the published component index of @nikolas.sapa/ns-ui and of @nikolas.sapa/ns-ui-mcp (each package read from its own tarball, never from the other’s), and one public Convex query, refreshed hourly. The daily bars come from recorded snapshots only; days before recording began stay grey.