herotransitions/hero vs overtake/telegramswift
herotransitions/hero shows stronger signals overall
As of June 2026, hero shows healthier maintenance signals than telegramswift. hero rates Healthy overall while telegramswift rates Mixed. hero last saw a commit 1 year ago with 26+ active contributors, while telegramswift last saw a commit 9 months ago with 1+ active contributor. hero is MIT-licensed while telegramswift is GPL-2.0-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.
herotransitions/hero →
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.
- ⚠Stale — last commit 1y ago
- ⚠Concentrated ownership — top contributor handles 62% of recent commits
- ✓26+ active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
overtake/telegramswift →
Slowing — last commit 8mo ago
copyleft license (GPL-2.0) — review compatibility; single-maintainer (no co-maintainers visible)…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 8mo ago; no CI workflows detected
- ⚠Slowing — last commit 8mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠GPL-2.0 is copyleft — check downstream compatibility
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓Last commit 8mo ago
- ✓GPL-2.0 licensed
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- →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
Signal-by-signal breakdown
| hero | telegramswift | |
|---|---|---|
| Stars | 22,452 | 5,667 |
| Last commit | 1y ago | 9mo ago |
| License | MIT | GPL-2.0 |
| Open issues | 42 | 901 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | — | — |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? herotransitions/hero · overtake/telegramswift
Ask AI about herotransitions/hero vs overtake/telegramswift
Open the chat with a comparison question pre-filled.