jakesgordon/javascript-state-machine vs sveltejs/kit
sveltejs/kit shows stronger signals overall
As of June 2026, kit shows healthier maintenance signals than javascript-state-machine. kit rates Healthy overall while javascript-state-machine rates Mixed. javascript-state-machine last saw a commit 1 year ago with 11+ active contributors, while kit was committed to 1 day ago with 37+ 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.
jakesgordon/javascript-state-machine →
Slowing — last commit 11mo 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 11mo ago; Scorecard "Branch-Protection" is 0/10
- ⚠Slowing — last commit 11mo ago
- ⚠Single-maintainer risk — top contributor 85% of recent commits
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 11mo ago
- ✓11 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
sveltejs/kit →
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 0/10; 2 cyclic import chains detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓37+ active contributors
- ✓Distributed ownership (top contributor 22% 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
| javascript-state-machine | kit | |
|---|---|---|
| Stars | 8,751 | 20,623 |
| Last commit | 1y ago | 1d ago |
| License | MIT | MIT |
| Open issues | 74 | 953 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 88% | 100% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | A |
| Cycles | — | 2 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? jakesgordon/javascript-state-machine · sveltejs/kit
Ask AI about jakesgordon/javascript-state-machine vs sveltejs/kit
Open the chat with a comparison question pre-filled.