bvaughn/react-virtualized vs facebook/react
facebook/react shows stronger signals overall
As of June 2026, react shows healthier maintenance signals than react-virtualized. react rates Healthy overall while react-virtualized rates Mixed. react-virtualized last saw a commit 1 year ago with 33+ active contributors, while react was committed to 1 day ago with 34+ 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.
bvaughn/react-virtualized →
Stale — last commit 1y ago
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 1y ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Stale — last commit 1y ago
- ⚠Scorecard: marked unmaintained (1/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓33+ active contributors
- ✓Distributed ownership (top contributor 31% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days; 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 OpenSSF Scorecard
facebook/react →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 1/10; 8 cyclic import chains — pervasive coupling
- ⚠Scorecard: default branch unprotected (1/10)
- ✓Last commit 1d ago
- ✓34+ active contributors
- ✓Distributed ownership (top contributor 17% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → 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
| react-virtualized | react | |
|---|---|---|
| Stars | 27,072 | 246,140 |
| Last commit | 1y ago | 1d ago |
| License | MIT | MIT |
| Open issues | 0 | 1,269 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 3% | 9% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 8 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? bvaughn/react-virtualized · facebook/react
Ask AI about bvaughn/react-virtualized vs facebook/react
Open the chat with a comparison question pre-filled.