endoflife-date/endoflife.date vs splitrb/split
endoflife-date/endoflife.date shows stronger signals overall
As of September 2026, endoflife.date shows healthier maintenance signals than split. endoflife.date rates Healthy overall while split rates Mixed. endoflife.date was committed to 1 week ago with 21+ active contributors, while split was committed to 1 week ago with 8+ 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.
endoflife-date/endoflife.date
Healthy across all four use cases
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ✓Last commit today
- ✓21+ active contributors
- ✓Distributed ownership (top contributor 40% 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 dependency CVEs from deps.dev and OpenSSF Scorecard
splitrb/split
Single-maintainer risk — review before adopting
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠Single-maintainer risk — top contributor 88% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit today
- ✓8 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
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
| endoflife.date | split | |
|---|---|---|
| Stars | 3,369 | 2,707 |
| Last commit | 10d ago | 9d ago |
| License | MIT | MIT |
| Open issues | 390 | 35 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 7% | 89% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 0 | 0 |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? endoflife-date/endoflife.date · splitrb/split
Ask AI about endoflife-date/endoflife.date vs splitrb/split
Open the chat with a comparison question pre-filled.