shadowsocks/shadowsocks-windows vs sta/websocket-sharp
Both showing Mixed signals — pick on fit, not health
As of June 2026, shadowsocks-windows and websocket-sharp both show mixed maintenance signals. shadowsocks-windows last saw a commit 1 year ago with 11+ active contributors, while websocket-sharp last saw a commit 2 months ago with 1+ active contributor. shadowsocks-windows is Other-licensed while websocket-sharp 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.
shadowsocks/shadowsocks-windows →
Stale — last commit 1y ago
non-standard license (Other); last commit was 1y ago…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 1y ago; no CI workflows detected
- ⚠Stale — last commit 1y ago
- ⚠Non-standard license (Other) — review terms
- ⚠No CI workflows detected
- ✓11 active contributors
- ✓Distributed ownership (top contributor 44% of recent commits)
- ✓Other licensed
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
- →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
sta/websocket-sharp →
Solo project — review before adopting
single-maintainer (no co-maintainers visible); no tests detected…
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)
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓Last commit 3w ago
- ✓MIT licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: onboard a second core maintainer; add a test suite
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| shadowsocks-windows | websocket-sharp | |
|---|---|---|
| Stars | 59,548 | 6,058 |
| Last commit | 1y ago | 2mo ago |
| License | Other | MIT |
| Open issues | 200 | 559 |
| Has tests | ✓ | — |
| Has CI | — | — |
| Test coverage | 12% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? shadowsocks/shadowsocks-windows · sta/websocket-sharp
Ask AI about shadowsocks/shadowsocks-windows vs sta/websocket-sharp
Open the chat with a comparison question pre-filled.