huiyadanli/revokemsgpatcher vs shadowsocksr-backup/shadowsocksr-csharp
Both showing Mixed signals — pick on fit, not health
As of June 2026, revokemsgpatcher and shadowsocksr-csharp both show mixed maintenance signals. revokemsgpatcher last saw a commit 1 month ago with 5+ active contributors, while shadowsocksr-csharp last saw a commit 7 years ago with 2+ active contributors. Both use the GPL-3.0 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.
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)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
shadowsocksr-backup/shadowsocksr-csharp →
Stale — last commit 7y ago
copyleft license (GPL-3.0) — review compatibility; last commit was 7y ago…
no CI workflows detected; no description (proxy for README missing)…
no description (proxy for README missing); last commit was 7y ago
last commit was 7y ago; no CI workflows detected
- ⚠Stale — last commit 7y ago
- ⚠Small team — 2 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 99% of recent commits
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠No CI workflows detected
- ✓2 active contributors
- ✓GPL-3.0 licensed
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- →Fork & modify Mixed → Healthy if: wire up GitHub Actions or equivalent
- →Learn from Mixed → Healthy if: add a README + repo description
- →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
| revokemsgpatcher | shadowsocksr-csharp | |
|---|---|---|
| Stars | 37,597 | 4,511 |
| Last commit | 1mo ago | 7y ago |
| License | GPL-3.0 | GPL-3.0 |
| Open issues | 51 | 10 |
| Has tests | — | ✓ |
| Has CI | ✓ | — |
| Test coverage | 0% | 4% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? huiyadanli/revokemsgpatcher · shadowsocksr-backup/shadowsocksr-csharp
Ask AI about huiyadanli/revokemsgpatcher vs shadowsocksr-backup/shadowsocksr-csharp
Open the chat with a comparison question pre-filled.