caldis/mos vs overtake/telegramswift
Both showing Mixed signals — pick on fit, not health
As of June 2026, mos and telegramswift both show mixed maintenance signals. mos last saw a commit 1 month ago with 1+ active contributor, while telegramswift last saw a commit 9 months ago with 1+ active contributor. mos is Other-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.
caldis/mos →
Solo project — review before adopting
non-standard license (Other); 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.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠Non-standard license (Other) — review terms
- ✓Last commit 1d ago
- ✓Other licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
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
| mos | telegramswift | |
|---|---|---|
| Stars | 20,047 | 5,667 |
| Last commit | 1mo ago | 9mo ago |
| License | Other | GPL-2.0 |
| Open issues | 360 | 901 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 100% | — |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? caldis/mos · overtake/telegramswift
Ask AI about caldis/mos vs overtake/telegramswift
Open the chat with a comparison question pre-filled.