communitytoolkit/windowscommunitytoolkit vs shadowsocks/shadowsocks-windows
Both showing Mixed signals — pick on fit, not health
As of September 2026, windowscommunitytoolkit and shadowsocks-windows both show mixed maintenance signals. windowscommunitytoolkit last saw a commit 1 year ago with 12+ active contributors, while shadowsocks-windows last saw a commit 1 year ago with 11+ active contributors. windowscommunitytoolkit is MIT-licensed while shadowsocks-windows is GPL-3.0-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.
communitytoolkit/windowscommunitytoolkit
Stale — last commit 2y ago
last commit was 2y ago; no tests detected in the complete Git tree…
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 0/10…
- ⚠Stale — last commit 2y ago
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓12 active contributors
- ✓Distributed ownership (top contributor 43% of recent commits)
- ✓MIT licensed
- ✓CI configured
What would improve this?
- •Use as dependency Mixed to Healthy if: 1 commit in the last 365 days
- •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
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
Signal-by-signal breakdown
| windowscommunitytoolkit | shadowsocks-windows | |
|---|---|---|
| Stars | 6,070 | 59,569 |
| Last commit | 1y ago | 1y ago |
| License | MIT | GPL-3.0 |
| Open issues | 314 | 203 |
| Has tests | No | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 0% | 9% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 0 | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? communitytoolkit/windowscommunitytoolkit · shadowsocks/shadowsocks-windows
Ask AI about communitytoolkit/windowscommunitytoolkit vs shadowsocks/shadowsocks-windows
Open the chat with a comparison question pre-filled.