cyanfish/naps2 vs shadowsocks/shadowsocks-windows
Both showing Mixed signals — pick on fit, not health
As of June 2026, naps2 and shadowsocks-windows both show mixed maintenance signals. naps2 last saw a commit 8 months ago with 1+ active contributor, while shadowsocks-windows last saw a commit 1 year ago with 11+ active contributors. Both use the Other license. 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.
cyanfish/naps2 →
Slowing — last commit 7mo ago
non-standard license (Other); single-maintainer (no co-maintainers visible)
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.
- ⚠Slowing — last commit 7mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠Non-standard license (Other) — review terms
- ✓Last commit 7mo ago
- ✓Other licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
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
Signal-by-signal breakdown
| naps2 | shadowsocks-windows | |
|---|---|---|
| Stars | 4,154 | 59,548 |
| Last commit | 8mo ago | 1y ago |
| License | Other | Other |
| Open issues | 236 | 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? cyanfish/naps2 · shadowsocks/shadowsocks-windows
Ask AI about cyanfish/naps2 vs shadowsocks/shadowsocks-windows
Open the chat with a comparison question pre-filled.