facebook/react vs ruanyf/webpack-demos
facebook/react shows stronger signals overall
As of June 2026, react shows healthier maintenance signals than webpack-demos. react rates Healthy overall while webpack-demos rates Concerns. react was committed to 1 day ago with 34+ active contributors, while webpack-demos last saw a commit 5 years ago with 23+ active contributors. 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 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
ruanyf/webpack-demos →
Stale and unlicensed — last commit 5y ago
no license — legally unclear; last commit was 5y ago…
no license — can't legally use code; no tests detected…
Documented and popular — useful reference codebase to read through.
no license — can't legally use code; last commit was 5y ago…
- ⚠Stale — last commit 5y ago
- ⚠Concentrated ownership — top contributor handles 61% of recent commits
- ⚠No license — legally unclear to depend on
- ⚠No CI workflows detected
- ⚠No test directory detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓23+ active contributors
What would improve this?
- →Use as dependency Concerns → Mixed if: publish a permissive license (MIT, Apache-2.0, etc.)
- →Fork & modify Concerns → Mixed if: add a LICENSE file
- →Deploy as-is Concerns → Mixed if: add a LICENSE file
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| react | webpack-demos | |
|---|---|---|
| Stars | 246,140 | 9,572 |
| Last commit | 1d ago | 5y ago |
| License | MIT | — |
| Open issues | 1,269 | 0 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 9% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | — |
| Cycles | 8 | — |
| Bottom-line | Healthy signals | Concerns signals |
Want the full analysis? facebook/react · ruanyf/webpack-demos
Ask AI about facebook/react vs ruanyf/webpack-demos
Open the chat with a comparison question pre-filled.