# openui/open-ui

Maintain an open standard for UI and promote its adherence and adoption.

Repository: https://github.com/openui/open-ui
Canonical: https://ross.abutalabs.com/products/open-ui
Homepage: https://open-ui.org
Language: MDX
License: NOASSERTION
License Family: other
Topics: ui, ux, w3c, standards, web-components
Last push: 2026-08-25T16:33:32+00:00

## Health v2 (maintenance only)
Score: 77/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 35, longevity 100
- inputs: {"age_days": 2666, "days_push": 8, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4512, forks 225 (observed 2026-08-28T04:08:52.615754+00:00)

## What it is
Open UI is a W3C Community Group project that maintains an open standard for web UI controls, specifying the parts, states, behaviors, and accessibility requirements of built-in components like selects, checkboxes, and date pickers. The repository hosts the specifications, research, and documentation site, with the goal of improving the web platform's native UI controls.

## Use cases
- standardize how built-in web UI controls like select dropdowns behave and can be styled
- research how design systems implement common UI components across the web
- contribute to W3C specifications for new HTML form controls
- find accessibility requirements for web UI components
- track proposals for extensible web UI controls and polyfills
- learn about the history and future of HTML form controls

## When to choose
- you are building or contributing to web standards and UI component specifications
- you design design systems and want research on common UI component patterns
- you want to follow or influence the evolution of native HTML controls

## When to avoid
- you need a ready-to-use component library or framework for shipping UI today
- you want runnable code rather than specifications and documentation
- you need a polyfill implementation itself rather than the standard behind it

## Facets
- artifact type: learning-resource
- maturity: active
- function: ui-components, documentation, web-framework
- domain: web-development, frontend, web-design, accessibility, documentation
- platform: browser, cross-platform
- tags: w3c, standards, web-components, specifications, polyfills, design-systems, community-group, web-server

## Member repositories
- openui/open-ui (main) score 77

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:52.615754+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:20:20.251038+00:00, confidence not recorded.
  - readme: https://github.com/openui/open-ui (fetched 2026-08-28T04:08:52.615754+00:00, sha d62039c9c5cf)
  - homepage: https://open-ui.org (fetched 2026-08-29T09:06:32.414550+00:00, sha 10c569844da1)
- Data as of 2026-08-30T08:39:29.467469+00:00.