RepoPilot

facebook/react vs sindresorhus/p-limit

facebook/react shows stronger signals overall

As of September 2026, react shows healthier maintenance signals than p-limit. react rates Healthy overall while p-limit rates Mixed. react was committed to 1 week ago with 26+ active contributors, while p-limit was committed to 2 weeks ago with 20+ active contributors. Both use the MIT license. Neither has known critical or high-severity CVEs in its dependency tree.

Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.

facebook/react

Healthy

Strong maintenance signals

MixedDependency

dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

dependency CVE scan unavailable

  • Last commit today
  • 26+ active contributors
  • Distributed ownership (top contributor 24% of recent commits)
  • MIT licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

sindresorhus/p-limit

Mixed

Mixed signals — read the receipts

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10

  • Concentrated ownership — top contributor handles 74% of recent commits
  • No tests detected in the complete Git tree
  • Scorecard: default branch unprotected (0/10)
  • Last commit 2w ago
  • 20 active contributors
  • MIT licensed
  • CI configured

What would improve this?

  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

reactp-limit
Stars249,6402,925
Last commit7d ago16d ago
LicenseMITMIT
Open issues1,3570
Has testsNo
Has CI
Test coverage100%0%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeA
Cycles0
Bottom-lineHealthy signalsMixed signals

Want the full analysis? facebook/react · sindresorhus/p-limit

Ask AI about facebook/react vs sindresorhus/p-limit

Open the chat with a comparison question pre-filled.