RepoPilot

stalwartlabs/stalwart vs ultraworkers/claw-code

ultraworkers/claw-code shows stronger signals overall

As of June 2026, claw-code shows healthier maintenance signals than stalwart. claw-code rates Healthy overall while stalwart rates Mixed. stalwart last saw a commit 1 month ago with 1+ active contributor, while claw-code was committed to 1 day ago with 10+ active contributors. 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.

stalwartlabs/stalwart

Mixed

Missing license — unclear to depend on

ConcernsDependency

no license — legally unclear; single-maintainer (no co-maintainers visible)

ConcernsFork & modify

no license — can't legally use code

HealthyLearn from

Documented and popular — useful reference codebase to read through.

ConcernsDeploy as-is

no license — can't legally use code

  • Solo or near-solo (1 contributor active in recent commits)
  • No license — legally unclear to depend on
  • Last commit today
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: publish a permissive license (MIT, Apache-2.0, etc.)
  • Fork & modify ConcernsMixed if: add a LICENSE file
  • Deploy as-is ConcernsMixed if: add a LICENSE file

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

ultraworkers/claw-code

Healthy

Healthy across the board

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

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 71% of recent commits
  • Last commit 1d ago
  • 10 active contributors
  • MIT licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

stalwartclaw-code
Stars12,669194,369
Last commit1mo ago1d ago
LicenseMIT
Open issues14820
Has tests
Has CI
Test coverage1%17%
Dependency CVEsNo CVEs0 critical · 0 high · 1 moderate · 0 low
Architecture grade
Cycles
Bottom-lineMixed signalsHealthy signals

Want the full analysis? stalwartlabs/stalwart · ultraworkers/claw-code

Ask AI about stalwartlabs/stalwart vs ultraworkers/claw-code

Open the chat with a comparison question pre-filled.