Assessment methodology

How ecosystem support is assessed

The current public model tracks contribution activity across 63 repositories and pairs metrics with review before support decisions are published.

Method status

Published inputs before rankings

Scores and allocations should not appear as public rankings until their data sources, time window, eligibility policy, and review limits are documented for the relevant reporting period.

Scoring model

Evidence is useful only when its limits are visible.

01

Contribution score

PRs × 8 + Issues × 3 + Commits × 1. This formula recognizes public GitHub activity while acknowledging that reviews, triage, discussions, and maintainer context require additional judgment.

02

Library impact

Funding review can consider ecosystem footprint, maintenance load, security posture, documentation, community benefit, and the role a project plays across React workflows.

03

Funding distribution

When an approved pool exists, distribution can be proportional to contribution scores and impact metrics after eligibility review. Public pages should identify the reporting period, inputs, limits, and any material human judgment.

04

Human review

Metrics structure the process but do not replace maintainer feedback, community input, or governance review.

Copyright © React a Series of LF Projects, LLC and its contributors. For web site terms of use, trademark policy and other project policies please see lfprojects.org.