An open source design system that's fully customizable and agent ready
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 81%
Response Time: 3d
First Timer Success: 64%
facebook/astryx has a recorded first-timer success rate of 64.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in facebook/astryx respond to incoming external pull requests in approximately 62.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 64.3 places facebook/astryx in the A tier.
The external contributor pull request merge rate for facebook/astryx is 81.2%, based on public PR activity from non-core contributors.
facebook/astryx currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An open source design system that's fully customizable and agent ready
Collaborative maintainer environment in facebook/astryx. Reviews community pull requests with focus on project quality.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/facebook/astryx?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~41 hours (96% approval). Large PRs (>500 lines) take ~300 hours (37% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in TypeScript.
Web GUI for tmux optimized for AI agent TUIs, with support for iOS safari and mac w/ keyboard shortcuts
Pokemon Auto Chess Game. Made by fans for fans. Open source, non profit. All rights to the Pokemon Company.
Command line tools for working with MyST Markdown.
packages/cli/foundation/discovery/template-adapter.mjs decides whether a scaffolded asset is a video by reading its extension. An extension it does not recognise falls through to the image placeholder silently, so the failure points at "broken content" rather than erroring. Two ways in: DEMO_ASSET_PATTERN (:182) is /\/template-assets\/[\w-]+\.(\w+)/g — it reads the extension off the first dot, so clip.min.mp4 is judged on min VIDEO_EXTENSIONS (:169) has no m4v Measured on main: 150 /template-assets/ references, none with a second dot, none .m4v — neither path reaches anyone today. Filed for the silent fall-through itself, not for the two cases. Found by @AKnassa in #4839, which was closed as superseded by #4863.
Problem A genuinely fresh worktree still cannot run pnpm -F @astryxdesign/storybook dev, even after #5100 fixed the @astryxdesign/richtext resolution. Storybook now fails earlier, on its own config load: Cannot find package '@astryxdesign/build/vite' imported from apps/storybook/.storybook/main.ts apps/storybook/.storybook/main.ts imports astryxStylex from @astryxdesign/build/vite, whose export map resolves to packages/build/dist/vite.mjs. That file does not exist until pnpm -F @astryxdesign/build build has run. Why a Vite alias cannot fix this one This is the Storybook config loader's node ESM resolution, not Vite's module graph — the failure happens while loading main.ts itself, before any resolve.alias from that file is in play. So the fix that worked for richtext (#5100) is structurally unavailable here. Noted as out of scope by @jiunshinn in #5100 and confirmed independently: the #5092 reporter's repro happened to have packages/build already compiled, which is why it surfaced r
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to facebook/astryx, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of facebook/astryx acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.2% were successfully merged into the primary branch.
facebook/astryx has a recorded first-timer success rate of 64.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 64.3 places facebook/astryx in the Welcoming tier.
The external pull request merge rate is 81.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, facebook/astryx currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for facebook/astryx are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.