facebook/astryx

An open source design system that's fully customizable and agent ready

Owned by Meta

View on GitHub ↗Jump to charts ↓Open shareable report →

facebook/astryx has 13k+ stars and 1k+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on July 8th, 2026
Created on January 9th, 2026
Open Issues & Pull Requests: 517 (+3)
GitHub issues: Enabled
Number of forks: 1,177
Total Stargazers: 13,688 (+1)
Total Subscribers: 90 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.1 hours
Mean response time: 7.4 days
90th percentile: 19.5 days
Tracked items: 1,381

Maintainer activity

15 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 6% of issues opened in the past year have never received a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "discussion" is answered fastest, typically in under an hour, while "documentation" waits about 3 days. 12% of tracked open issues have had no activity in three months. 82% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 255
New in 7 days: 21
Closed in 7 days: 29
Avg open age: 22 days
Stale 30+ days: 191
Stale 90+ days: 31

Recent activity

Opened in 7 days: 18
Closed in 7 days: 27
Comments in 7 days: 11
Events in 7 days: 63

Top labels

  • enhancement (441)
  • bug (324)
  • component (215)
  • vibe-test (111)
  • hardening (85)
  • vibe-test-nightly (65)
  • documentation (61)
  • discussion (43)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Astryx is a design system that ships 150+ accessible React components with brand-level theming, dark mode, and templates as a cohesive system built on React 19 and StyleX.

The tool solves the problem of building consistent interfaces across large numbers of applications while accommodating both human developers and AI assistants. It grew inside a large organization over eight years, powering thousands of applications shaped by engineers, designers, and product teams. Rather than locking components behind a closed API, Astryx exports its building blocks directly for composition at any level, and includes a swizzle feature that ejects a component's full source into your project when you need deeper customization. Styling is authored in StyleX but remains invisible to consumers, who can override with className using Tailwind, CSS modules, or plain CSS. Theming works through CSS custom property overrides, letting designers customize the appearance without forking component source or wrapping components.

Astryx suits teams building multiple applications who want a shared design language without styling lock-in or complex build configuration. The setup requires only CSS imports and a theme provider with no build plugin, PostCSS, or Babel configuration needed. It works with Next.js, Vite, and other frameworks. The tool includes a CLI for component documentation, templates, scaffolding, and codemods, designed so that both people and AI assistants use the same reference and tooling. Seven ready-made themes are provided as starting points for customization.

The project receives issue reports primarily from outside users rather than the core team, indicating a substantial base of adopters using it in production. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on enhancements, bug fixes, and component-related tasks.