RepoPilot

dotnet-state-machine/stateless vs huiyadanli/revokemsgpatcher

Both showing Mixed signals — pick on fit, not health

As of June 2026, stateless and revokemsgpatcher both show mixed maintenance signals. stateless last saw a commit 2 months ago with 15+ active contributors, while revokemsgpatcher last saw a commit 1 month ago with 5+ active contributors. stateless is Other-licensed while revokemsgpatcher 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.

dotnet-state-machine/stateless

Mixed

Mixed signals — read the receipts

ConcernsDependency

non-standard license (Other)

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Concentrated ownership — top contributor handles 70% of recent commits
  • Non-standard license (Other) — review terms
  • Last commit 5w ago
  • 15 active contributors
  • Other licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: clarify license terms

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

huiyadanli/revokemsgpatcher

Mixed

Single-maintainer risk — review before adopting

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; top contributor handles 94% of recent commits…

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

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 ConcernsMixed 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

Signal-by-signal breakdown

statelessrevokemsgpatcher
Stars6,17037,597
Last commit2mo ago1mo ago
LicenseOtherGPL-3.0
Open issues8151
Has tests
Has CI
Test coverage50%0%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineMixed signalsMixed signals

Want the full analysis? dotnet-state-machine/stateless · huiyadanli/revokemsgpatcher

Ask AI about dotnet-state-machine/stateless vs huiyadanli/revokemsgpatcher

Open the chat with a comparison question pre-filled.