keijiro/aicommand vs shadowsocks/shadowsocks-windows
shadowsocks/shadowsocks-windows shows stronger signals overall
As of June 2026, shadowsocks-windows shows stronger maintenance signals than aicommand. shadowsocks-windows rates Mixed overall while aicommand rates Concerns. aicommand last saw a commit 2 years ago with 1+ active contributor, while shadowsocks-windows last saw a commit 1 year ago with 11+ active contributors. aicommand is Unlicense-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.
keijiro/aicommand →
Looks unmaintained — solo project with stale commits
last commit was 2y ago; 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.
last commit was 2y ago; no CI workflows detected
- ⚠Stale — last commit 2y ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠No CI workflows detected
- ✓Unlicense licensed
- ✓Tests present
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days; onboard a second core maintainer
- →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
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
| aicommand | shadowsocks-windows | |
|---|---|---|
| Stars | 4,117 | 59,548 |
| Last commit | 2y ago | 1y ago |
| License | Unlicense | Other |
| Open issues | 6 | 200 |
| Has tests | ✓ | ✓ |
| Has CI | — | — |
| Test coverage | 50% | 12% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Concerns signals | Mixed signals |
Want the full analysis? keijiro/aicommand · shadowsocks/shadowsocks-windows
Ask AI about keijiro/aicommand vs shadowsocks/shadowsocks-windows
Open the chat with a comparison question pre-filled.