huiyadanli/revokemsgpatcher vs sta/websocket-sharp
Both showing Mixed signals — pick on fit, not health
As of June 2026, revokemsgpatcher and websocket-sharp both show mixed maintenance signals. revokemsgpatcher last saw a commit 1 month ago with 5+ active contributors, while websocket-sharp last saw a commit 2 months ago with 1+ active contributor. revokemsgpatcher is GPL-3.0-licensed while websocket-sharp is MIT-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.
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
sta/websocket-sharp →
Solo project — review before adopting
single-maintainer (no co-maintainers visible); no tests detected…
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.
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓Last commit 3w ago
- ✓MIT licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: onboard a second core maintainer; add a test suite
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| revokemsgpatcher | websocket-sharp | |
|---|---|---|
| Stars | 37,597 | 6,058 |
| Last commit | 1mo ago | 2mo ago |
| License | GPL-3.0 | MIT |
| Open issues | 51 | 559 |
| Has tests | — | — |
| Has CI | ✓ | — |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? huiyadanli/revokemsgpatcher · sta/websocket-sharp
Ask AI about huiyadanli/revokemsgpatcher vs sta/websocket-sharp
Open the chat with a comparison question pre-filled.