Meta's Astryx Design System Hits 19.7k Stars, Still in Beta

Meta's Astryx, an open-source React design system, had 19.7k GitHub stars, 1.5k forks and 301 open issues when The Terminal read the repository on Nov. 9, 2026, and its README still calls it "Currently in Beta." The figures that make it sound production-ready come from Meta itself.

The README describes Astryx as "the most-used and largest design system in the company," powering "13,000+ apps," and says it "grew inside Meta over the last eight years." It promises "150+ accessible components" with full TypeScript support, brand-level theming, dark mode, templates and a CLI. None of that scale or adoption data has been checked by anyone outside the company, and the page names no individual maintainer.

What you need to adopt it

Astryx requires React 19 or later and authors its styles with StyleX, Meta's compile-time CSS system. According to InfoQ's report by Bruno Couriol, published Sept. 13, components accept an xstyle prop for typed styling, and also accept className, so a team using Tailwind, CSS Modules or plain CSS does not need extra compiler setup. The core package ships pre-compiled CSS.

That last point is the practical one. A team does not have to adopt StyleX to try the library, and overrides arrive through the mechanisms they already use. Contributors, by contrast, need Node 22 or later and pnpm 11.

The pieces that are not stable

Package	Status per the README
Core components	Beta
@astryxdesign/vega	@canary dist-tag only, no stable release
@astryxdesign/charts	@canary dist-tag only, no stable release
@astryxdesign/lab	Not published to npm

A design system whose charting package is canary-only is a design system without a stable charts story. Anyone building dashboards on it today is pinning a pre-release.

Agent-ready, and the swizzle escape hatch

The repository description calls Astryx "agent ready," and the README claims that "both people and AI assistants build with the same tooling." InfoQ says that support runs through the CLI and an MCP endpoint, the protocol many coding agents use to call external tools. That claim is the vendor's own, and The Terminal did not run the tooling.

The CLI also has a swizzle command that copies a component's full source into your repository. InfoQ notes the trade: ejecting is sometimes necessary when customization needs private state, DOM structure or event listeners the public API does not expose, but it moves maintenance of that component to you.

Governance questions and forks

InfoQ reports that questions about long-term maintenance and governance of a Meta-sponsored framework have come up on Reddit, though it does not name who raised them. It also says developers have ported the token architecture and component specifications to Svelte 5 and Flutter, as community efforts rather than Meta releases.

For a team choosing a component library, the open question is whether the canary packages reach a stable tag. The Terminal's earlier reports on the Pi agent's move to AGENTS.md and on Dependabot's handling of agent manifests show agent support being added through configuration files. For Astryx, the README is where to check what is actually stable. The repository's 373 open pull requests are the place to watch.