@openstatus
Reliable 96/100 · #6 of 342 scoredHand-crafted, accessible components for building beautiful status pages.
@openstatus is a shadcn UI community registry. Its source repository is openstatusHQ/openstatus , which has 9.2k GitHub stars, 780 forks and 121 contributors. The last commit was today (348 commits in the last 90 days). It scores 96/100 on Sealambda's maturity index, placing it in the Reliable tier.
Maturity breakdown
last commit 0d ago · 348 commits/90d
9.2k★ · 780 forks
121 contributors · bus factor 2 · 31 watching
284/310 issues closed (92%)
AGPL-3.0 · 62% health files
Repository facts
- 9.2k
- Stars
- 780
- Forks
- 121
- Contributors
- 2
- Bus factor
- 26
- Open issues
- 284
- Closed issues
- 348
- Commits (90d)
- TypeScript
- Language
- AGPL-3.0
- License
- —
- Latest version
- none
- Releases
- today
- Last commit
License, pricing and purpose
- License
- AGPL-3.0 · ✓ OSI-approved
- Network copyleft: Like strong copyleft, and offering the software over a network also counts as distribution.
- Access
- FOSS
- An OSI-approved or FSF-libre license, and everything offered is free.
- Purpose
- A collection of shadcn/ui-compatible blocks and components for building custom status pages and incident timelines.
- Commercial model
- Free
- Everything the project offers is free to use, with no paid tier. Donations and sponsorships do not count as paid.
- Tied to a service
- No
- Yes when the components are a client for a commercial API or service.
- Scope
- Domain-specific
- Focused on one problem area, such as charts, AI chat, an editor, a status page or payments; an app adds it for that feature only.
- Domains
- Status & monitoring
- Status & monitoring: Status pages, uptime, monitoring and incident components.
- Design
- Vanilla shadcn
- Looks like default shadcn/ui: the same shapes, spacing, borders and neutral palette, at most with another accent color.
- Coverage
- 2%
- Share of shadcn/ui core primitives that the registry ships.
Evidence
-
“The openstatus registry provides production-ready React components specifically designed for status pages. Built on top of shadcn/ui , these components are accessible, customizable, and battle-tested”
commercial · homepage ↗ -
“The openstatus registry is a collection of shadcn/ui-compatible, pre-built components for common status page patterns.”
scope · homepage ↗ -
“Instead of building status indicators, event timelines, and monitoring displays from scratch, install and customize these components directly into your project.”
domains · homepage ↗ -
“Customizable - Fully themeable with Tailwind CSS”
design · homepage ↗
AI-suggested by google/gemini-3.8-flash@Google AI Studio on 2026-10-02
Install
Add components from this registry with the shadcn CLI (configure the registry URL in your
components.json):
pnpm dlx shadcn@latest add @openstatus/[component]
endpoint: https://openstatus.dev/r/{name}.json
Embed the maturity badge
Add a live maturity badge to your README:
[](https://shadcn.sealambda.com/registry/openstatus/)