shadowsocks/shadowsocks-windows vs sta/websocket-sharp
Both showing Mixed signals — pick on fit, not health
As of September 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 4 months ago with 1+ active contributor. shadowsocks-windows is GPL-3.0-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 2y ago
copyleft license (GPL-3.0) — review compatibility; last commit was 2y ago…
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; Scorecard "Branch-Protection" is 1/10…
- ⚠Stale — last commit 2y ago
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (1/10)
- ✓11 active contributors
- ✓Distributed ownership (top contributor 44% of recent commits)
- ✓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: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
sta/websocket-sharp
Solo project — review before adopting
single-maintainer (no co-maintainers visible); test evidence incomplete…
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
CI evidence incomplete; dependency CVE scan unavailable
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ✓Last commit 3w ago
- ✓MIT licensed
What would improve this?
- •Use as dependency Mixed to Healthy if: onboard a second core maintainer
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| shadowsocks-windows | websocket-sharp | |
|---|---|---|
| Stars | 59,569 | 6,058 |
| Last commit | 1y ago | 4mo ago |
| License | GPL-3.0 | MIT |
| Open issues | 203 | 559 |
| Has tests | ✓ | Unknown |
| Has CI | ✓ | Unknown |
| Test coverage | 9% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | — |
| Cycles | 0 | — |
| 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.