RepoPilot

devolutions/unigetui vs sta/websocket-sharp

Both showing Mixed signals — pick on fit, not health

As of September 2026, unigetui and websocket-sharp both show mixed maintenance signals. unigetui was committed to 1 week ago with 20+ active contributors, while websocket-sharp last saw a commit 4 months ago with 1+ active contributor. Both use the MIT 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.

devolutions/unigetui

Mixed

Mixed signals — read the receipts

MixedDependency

no tests detected in the complete Git tree; dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; dependency CVE scan unavailable

  • Concentrated ownership — top contributor handles 65% of recent commits
  • No tests detected in the complete Git tree
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 20 active contributors
  • MIT licensed
  • CI configured

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

sta/websocket-sharp

Mixed

Solo project — review before adopting

MixedDependency

single-maintainer (no co-maintainers visible); test evidence incomplete…

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

CI evidence incomplete; dependency CVE scan unavailable

  • Solo or near-solo (1 contributor active in recent commits)
  • Last commit 3w ago
  • MIT licensed

What would improve this?

  • Use as dependency Mixed to Healthy if: onboard a second core maintainer

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Signal-by-signal breakdown

unigetuiwebsocket-sharp
Stars25,9886,058
Last commit11d ago4mo ago
LicenseMITMIT
Open issues483559
Has testsNoUnknown
Has CIUnknown
Test coverage0%0%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeC
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? devolutions/unigetui · sta/websocket-sharp

Ask AI about devolutions/unigetui vs sta/websocket-sharp

Open the chat with a comparison question pre-filled.