glitchenzo/nugetforunity vs shadowsocks/shadowsocks-windows
glitchenzo/nugetforunity shows stronger signals overall
As of June 2026, nugetforunity shows healthier maintenance signals than shadowsocks-windows. nugetforunity rates Healthy overall while shadowsocks-windows rates Mixed. nugetforunity last saw a commit 2 months ago with 22+ active contributors, while shadowsocks-windows last saw a commit 1 year ago with 11+ active contributors. nugetforunity is MIT-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.
glitchenzo/nugetforunity →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
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.
- ⚠Concentrated ownership — top contributor handles 52% of recent commits
- ✓Last commit 3w ago
- ✓22+ active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
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
| nugetforunity | shadowsocks-windows | |
|---|---|---|
| Stars | 4,434 | 59,548 |
| Last commit | 2mo ago | 1y ago |
| License | MIT | Other |
| Open issues | 75 | 200 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | — |
| Test coverage | 100% | 12% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? glitchenzo/nugetforunity · shadowsocks/shadowsocks-windows
Ask AI about glitchenzo/nugetforunity vs shadowsocks/shadowsocks-windows
Open the chat with a comparison question pre-filled.