freecodecamp/freecodecamp vs statelyai/xstate
Both showing Healthy signals — pick on fit, not health
As of July 2026, freecodecamp and xstate both show healthy maintenance signals. freecodecamp was committed to 3 days ago with 56+ active contributors, while xstate was committed to today with 11+ active contributors. freecodecamp is BSD-3-Clause-licensed while xstate is MIT-licensed. 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.
freecodecamp/freecodecamp
Strong maintenance signals
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 "Token-Permissions" is 0/10; no CI workflows detected
- ⚠No CI workflows detected
- ⚠Scorecard: dangerous CI workflow (0/10)
- ✓Last commit today
- ✓56+ active contributors
- ✓Distributed ownership (top contributor 14% of recent commits)
- ✓BSD-3-Clause licensed
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Token-Permissions" 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
statelyai/xstate
Healthy across all four use cases
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.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Concentrated ownership — top contributor handles 53% of recent commits
- ✓Last commit today
- ✓11 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
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
| freecodecamp | xstate | |
|---|---|---|
| Stars | 451,315 | 29,850 |
| Last commit | 3d ago | today |
| License | BSD-3-Clause | MIT |
| Open issues | 220 | 122 |
| Has tests | ✓ | ✓ |
| Has CI | — | ✓ |
| Test coverage | 0% | 2% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | A | — |
| Cycles | 0 | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? freecodecamp/freecodecamp · statelyai/xstate
Ask AI about freecodecamp/freecodecamp vs statelyai/xstate
Open the chat with a comparison question pre-filled.