RepoPilot

trunk-rs/trunk vs ultraworkers/claw-code

Both showing Healthy signals — pick on fit, not health

As of September 2026, trunk and claw-code both show healthy maintenance signals. trunk was committed to 3 weeks ago with 21+ active contributors, while claw-code last saw a commit 1 month ago with 11+ active contributors. trunk is Apache-2.0-licensed while claw-code 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.

trunk-rs/trunk

Healthy

Strong maintenance signals

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

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; 8 cyclic import chains — pervasive coupling

  • Scorecard: default branch unprotected (0/10)
  • Last commit 2w ago
  • 21+ active contributors
  • Distributed ownership (top contributor 36% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

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

ultraworkers/claw-code

Healthy

Healthy across all four use cases

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

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

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Concentrated ownership — top contributor handles 65% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 3w ago
  • 11 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

trunkclaw-code
Stars4,389195,190
Last commit21d ago1mo ago
LicenseApache-2.0MIT
Open issues13641
Has tests
Has CI
Test coverage8%13%
Dependency CVEsNo CVEs0 critical · 0 high · 1 moderate · 0 low
Architecture gradeCA
Cycles80
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? trunk-rs/trunk · ultraworkers/claw-code

Ask AI about trunk-rs/trunk vs ultraworkers/claw-code

Open the chat with a comparison question pre-filled.