RepoPilot

killercup/cargo-edit vs ultraworkers/claw-code

Both showing Healthy signals — pick on fit, not health

As of June 2026, cargo-edit and claw-code both show healthy maintenance signals. cargo-edit last saw a commit 2 months ago with 6+ active contributors, while claw-code was committed to 1 day ago with 10+ active contributors. 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.

killercup/cargo-edit

Healthy

Healthy across all four use cases

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.

  • Single-maintainer risk — top contributor 95% of recent commits
  • Last commit 3w ago
  • 6 active contributors
  • MIT licensed
  • CI configured
  • Tests present

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

cargo-editclaw-code
Stars3,402194,369
Last commit2mo ago1d ago
LicenseMITMIT
Open issues7020
Has tests
Has CI
Test coverage100%17%
Dependency CVEsNo CVEs0 critical · 0 high · 1 moderate · 0 low
Architecture grade
Cycles
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? killercup/cargo-edit · ultraworkers/claw-code

Ask AI about killercup/cargo-edit vs ultraworkers/claw-code

Open the chat with a comparison question pre-filled.