huiyadanli/revokemsgpatcher vs shadowsocks/shadowsocks-windows
Both showing Mixed signals — pick on fit, not health
As of June 2026, revokemsgpatcher and shadowsocks-windows both show mixed maintenance signals. revokemsgpatcher last saw a commit 1 month ago with 5+ active contributors, while shadowsocks-windows last saw a commit 1 year ago with 11+ active contributors. revokemsgpatcher is GPL-3.0-licensed while shadowsocks-windows is Other-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.
huiyadanli/revokemsgpatcher →
Single-maintainer risk — review before adopting
copyleft license (GPL-3.0) — review compatibility; top contributor handles 94% of recent commits…
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.
- ⚠Single-maintainer risk — top contributor 94% of recent commits
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠No test directory detected
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 3d ago
- ✓5 active contributors
- ✓GPL-3.0 licensed
- ✓CI configured
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests + OpenSSF Scorecard
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
Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| revokemsgpatcher | shadowsocks-windows | |
|---|---|---|
| Stars | 37,597 | 59,548 |
| Last commit | 1mo ago | 1y ago |
| License | GPL-3.0 | Other |
| Open issues | 51 | 200 |
| Has tests | — | ✓ |
| Has CI | ✓ | — |
| Test coverage | 0% | 12% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? huiyadanli/revokemsgpatcher · shadowsocks/shadowsocks-windows
Ask AI about huiyadanli/revokemsgpatcher vs shadowsocks/shadowsocks-windows
Open the chat with a comparison question pre-filled.