sagernet/sing-box vs yaoapp/yao
Both showing Mixed signals — pick on fit, not health
As of September 2026, sing-box and yao both show mixed maintenance signals. sing-box was committed to 1 day ago with 2+ active contributors, while yao was committed to 1 week ago with 2+ active contributors. 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
yaoapp/yao
Single-maintainer risk — review before adopting
top contributor handles 99% of recent commits; license evidence incomplete…
license evidence incomplete
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; license evidence incomplete…
- ⚠Small team — 2 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 99% of recent commits
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2d ago
- ✓2 active contributors
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| sing-box | yao | |
|---|---|---|
| Stars | 37,880 | 7,900 |
| Last commit | 1d ago | 7d ago |
| License | GPL-3.0 | Unknown |
| Open issues | 327 | 7 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 12% | 68% |
| Dependency CVEs | 0 critical · 0 high · 9 moderate · 0 low | No CVEs |
| Architecture grade | — | C |
| Cycles | — | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? sagernet/sing-box · yaoapp/yao
Ask AI about sagernet/sing-box vs yaoapp/yao
Open the chat with a comparison question pre-filled.