sagernet/sing-box vs usefathom/fathom
Both showing Mixed signals — pick on fit, not health
As of September 2026, sing-box and fathom both show mixed maintenance signals. sing-box was committed to 6 days ago with 2+ active contributors, while fathom last saw a commit 6 months ago with 15+ active contributors. sing-box is GPL-3.0-licensed while fathom 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.
sagernet/sing-box
Single-maintainer risk — review before adopting
copyleft license (GPL-3.0) — review compatibility; top contributor handles 99% of recent commits
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
- ⚠Small team — 2 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 99% of recent commits
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2d ago
- ✓2 active contributors
- ✓GPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- •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
usefathom/fathom
Slowing — last commit 6mo ago
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
- ⚠Slowing — last commit 6mo ago
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 6mo ago
- ✓15 active contributors
- ✓Distributed ownership (top contributor 49% of recent commits)
- ✓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
| sing-box | fathom | |
|---|---|---|
| Stars | 37,880 | 8,018 |
| Last commit | 6d ago | 6mo ago |
| License | GPL-3.0 | MIT |
| Open issues | 327 | 5 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 12% | 20% |
| Dependency CVEs | 0 critical · 0 high · 9 moderate · 0 low | No CVEs |
| Architecture grade | — | A |
| Cycles | — | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? sagernet/sing-box · usefathom/fathom
Ask AI about sagernet/sing-box vs usefathom/fathom
Open the chat with a comparison question pre-filled.