Sixty components in twelve categories, each installed as source you own.
Every component is shipped, which means its source installs and renders and its API may change in any release. Each was audited against WCAG 2.2 AA by its own authors. None has had an independent accessibility review or a clinical review, so none is ready for a production health surface.
The CLI copies the component's source and the opsinjs lib/ files it reads into your project, and adds its npm dependencies. <name> is the id in each link below. Add the @opsinjs entry to components.json first, as Getting started shows.
Start from your data, and from who assigned any status it carries.
A measurement the reader interprets is a ResultCard, or a RangeBar when its place in the range is the point. A MetricTile that needs interpreting is a ResultCard at the wrong size.
A ScoreDial implies a composite index, so it never shows a single measurement.
Status appears only where a rule your product owns assigned it, and no component computes one. A category, a trend or a position against a range is not a status. See Two colour axes.
Allow at most one urgent surface per screen. See Alerts.
Decide what each component renders in all five data states: empty, loading, error, stale and partial. See States.
Not written yet.
A rule for choosing between input components. Until then, read each component's page.
You copy source, so you ship only what you import. Per-component sizes are not measured yet. The limit more likely to bite is the budget of three overlapping composited surfaces in Materials.
This table has not been generated. It is produced by scripts/build-registry.mts. Run pnpm run generate and reload.
Nothing on this site types a measured number by hand, so an ungenerated table shows this rather than an example.