Awesome Open Source logo
Awesome Open Source
Sign in Create account

adobe/react-spectrum

A collection of libraries and tools that help you build adaptive, accessible, and robust user experiences.

20
Hotness score
79
Reliability score
15,693
Stars
almost 7 years
Age
0
Published reviews
0
Questions

Scores

Hotness and reliability

The two headline scores, measured daily, with 30, 90, and 180 day views.

Hotness score

Jul 19, 2026

Current20

Previous20

Weekly average

100500
Full metrics details

Derived only from GitHub GraphQL starredAt events after daily star totals are reconciled.

180 observed daily rows. Missing days are not fabricated.

Hotness formula

40% Hot today + 40% Hot this week + 20% Breakout.

  • 40% Hot today: 16
  • 40% Hot this week: 31
  • 20% Breakout: 1
  • Stars gained: 1d: 4
  • Stars gained: 7d: 32
  • Stars gained: 14d: 65
  • Stars gained: 30d: 152
  • Stars gained: 90d: 739

Per-day formula: 0.40 × Hot today + 0.40 × Hot week + 0.20 × Breakout.

  • Same-day multiplier = stars 1d ÷ max(1, stars 7d ÷ 7)
  • Weekly multiplier = stars 7d ÷ max(1, stars 30d ÷ 30 × 7)
  • Fortnight multiplier = stars 14d ÷ max(1, stars 90d ÷ 90 × 14)
  • Hot today = clamp(70 × log-scale(stars 1d, 1000) + 30 × breakout-scale(same-day, 4))
  • Hot week = clamp(75 × log-scale(stars 7d, 5000) + 25 × breakout-scale(weekly, 3))
  • Breakout = clamp(35 × breakout-scale(same-day, 4) + 40 × breakout-scale(weekly, 3) + 25 × breakout-scale(fortnight, 2.5))
DateStarsStars 1dStars 7dStars 14dStars 30dStars 90dSame-day multiplierWeekly multiplierFortnight multiplierHot todayHot weekBreakoutStored score

Reliability score

Jul 19, 2026

Current79

Previous81

Weekly average

100500
Full metrics details

Derived from the displayed continuity, closure, shipping, liveness, and support-burden components.

180 observed daily rows. Missing days are not fabricated.

Reliability formula

30% Continuity + 30% Closure + 20% Shipping + 10% Liveness + 10% Support burden.

  • 30% Continuity: 86
  • 30% Closure: 89
  • 20% Shipping: 62
  • 10% Liveness: 100
  • 10% Support burden: 34

Per-day formula: 0.30 × Continuity + 0.30 × Closure + 0.20 × Shipping + 0.10 × Liveness + 0.10 × Support burden.

  • Continuity = 35% active ratio 90d + 20% active ratio 30d + 15% PR efficiency 90d + 10% PR efficiency 30d + 10% liveness + 10% observed-history coverage
  • Closure = 55% PR merge efficiency 90d + 45% issue close efficiency 90d
  • Shipping = 100 × (20% × release ratio 30d + 30% × release ratio 90d + 50% × release ratio 180d); ratios are releases ÷ 2, 6, and 12, capped at 1
  • Support burden = 100 − 2 × open issues per 1,000 stars
  • Liveness = 100 × exp(−pushed days ago ÷ 120)

Stars, issues, pull requests, and releases are daily observations. Pushed-days and license are repository snapshot-derived inputs and are not independent historical GitHub events.

DateIssues openedIssues closedPRs openedPRs mergedReleasesStarsOpen issuesPushed days agoContinuityClosureShippingLivenessSupport burdenLicenseObserved daysMissing daysNeeds healingStored score

Reliability breakdown

What drives the reliability score

Component scores measured daily from GitHub activity (2026-07-18).

Continuity30% of headline86

Activity on 80 of 90 tracked days in the last 90 and 27 of 30 in the last 30.

Activity pulse
Closure30% of headline89

Merged 194 of 247 PRs opened and closed 135 of 110 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.

PRs merged (90d)PRs opened (90d)Issues closed (90d)Issues opened (90d)
Shipping20% of headline62

10 releases in the last 180 days, 4 in the last 90 and 0 in the last 30 — a steady cadence scores highest.

Releases
Liveness10% of headline100

Last push 0 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).

Repository
Support burden10% of headline34

518 open issues against 15,693 stars — about 33 open issues per 1,000 stars. Lighter backlogs score higher.

Open issuesStargazers
Adoption confidence100

Modeled — how confidently teams are adopting this repo. Stargazers

Maintenance quality80

Modeled from PR/issue responsiveness and upkeep signals. Activity pulse

Risk score28

Modeled — lower is better; adoption and continuity risk. Repository

Stays active (30d)90%

Modeled chance the repo stays active over 30 days. Activity pulse

Stays active (90d)88%

Modeled chance the repo stays active over 90 days. Activity pulse

Release rhythm (180d)62

Regularity of releases over the last 180 days. Releases

Maintainer bus risk (90d)9%

Modeled — lower is better; concentration of commits in few maintainers. Contributors graph

Topics

Explore related topics

Jump into the topic listings this repository belongs to.

ReactUi Components

Measured history

Project metrics

Weekly GitHub totals with 30, 90, and 180 day views.

Weekly star gains

Jul 19, 2026

Current30

Previous31

Weekly star gains

21862-93
Full metrics details

GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue

Cumulative stars

Jul 19, 2026

Current15,689

Previous15,659

Cumulative total

15,6897,8450
Full metrics details

Running total of the GitHub GraphQL stargazer count over time (not weekly deltas), reconstructed from starredAt events and totalCount in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.

180 observed daily rows. Missing days are not fabricated.

DateValue

Issues opened

Jul 12, 2026

Current7

Previous7

Weekly total

1580
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

178 observed daily rows. Missing days are not fabricated.

DateValue

Issues closed

Jul 12, 2026

Current11

Previous4

Weekly total

40200
Full metrics details

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

178 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests opened

Jul 12, 2026

Current17

Previous16

Weekly total

38190
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

178 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests closed

Jul 12, 2026

Current21

Previous2

Weekly total

72360
Full metrics details

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

178 observed daily rows. Missing days are not fabricated.

DateValue

Pull requests merged

Jul 12, 2026

Current19

Previous0

Weekly total

39200
Full metrics details

GitHub API observation. Historical values render only when the source provides a real observation for that day.

178 observed daily rows. Missing days are not fabricated.

DateValue

Issue close ratio (daily)

Jul 17, 2026

Current3.00

Previous0.00

Daily ratio — a gap means nothing was opened that day

How this works: each day's value is issues closed that day ÷ issues opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more issues than arrived that day.

11.005.500.00
Full metrics details

GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.

118 observed daily rows. Missing days are not fabricated.

Per-day formula: issues closed that day ÷ issues opened that day; blank when nothing was opened (a gap, not a zero).

DateIssues openedIssues closedStored score

Pull request close ratio (daily)

Jul 17, 2026

Current3.00

Previous1.00

Daily ratio — a gap means nothing was opened that day

How this works: each day's value is pull requests closed that day ÷ pull requests opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more pull requests than arrived that day.

39.0019.500.00
Full metrics details

GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.

150 observed daily rows. Missing days are not fabricated.

Per-day formula: pull requests closed that day ÷ pull requests opened that day; blank when nothing was opened (a gap, not a zero).

DatePRs openedPRs closedStored score

Releases

Jul 19, 2026

Current0

Previous0

Weekly total

210
Full metrics details

GitHub release published_at events bucketed by UTC day; drafts are excluded.

180 observed daily rows. Missing days are not fabricated.

DateValue

About React Spectrum

<p>React Spectrum is Adobe's component layer built on top of React Aria and React Stately, combining accessible behavior, state logic, and polished visual components in one stack. It is designed for internationalized, keyboard-navigable applications where correctness matters as much as aesthetics. The APIs emphasize predictable composition, making it easier to build complex interactions without reinventing foundational UX behavior.</p>
<p>It is especially compelling when your team needs strong accessibility defaults and robust cross-input support from day one. Spectrum components inherit Adobe's design principles, but the lower-level Aria/Stately layers let you customize behavior without abandoning the ecosystem. For product teams balancing speed with compliance and long-term maintainability, React Spectrum is one of the safest architectural choices.</p>

Join the conversation

Reviews · Questions · Posts

Share what you know about react-spectrum — write a review from your real experience, ask an implementation question, or publish a post about how you use it.

Write a review Ask a question Write a post

Share your experience

Write or update your review

Explain what worked, what broke down, and what another team should know before adopting react-spectrum.

Sign in to review Create account

Write your review now — it saves locally and publishes automatically after you sign in.

Rating
Positive attributes
Negative attributes

Project Q&A

Questions and answers

Browse implementation threads tied directly to adobe/react-spectrum. Each question links through to the full answer page.

Q&A No threads yet

Be the first to ask how teams run react-spectrum in production. Every question you post becomes a durable, searchable answer page other developers can find.

Ask the first question

Related posts

Posts tagged with the same topics

These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.

Posts No topic-linked posts yet

Share how your team uses react-spectrum — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.

Write the first post
Get a weekly email with the hottest new projects in the Component Library and React Spectrum world.
No Spam. Unsubscribe easily at any time.
Privacy | About | Terms | Follow Us On Twitter

Copyright 2018-2026 Awesome Open Source.  All rights reserved.