RepoPilot

hyperium/hyper vs ultraworkers/claw-code

Both showing Healthy signals — pick on fit, not health

As of September 2026, hyper and claw-code both show healthy maintenance signals. hyper last saw a commit 4 months ago with 44+ active contributors, while claw-code was committed to 4 weeks ago with 11+ 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.

hyperium/hyper

Healthy

Strong maintenance signals

MixedDependency

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

dependency CVE scan unavailable

  • Last commit 3d ago
  • 44+ active contributors
  • Distributed ownership (top contributor 36% of recent commits)
  • 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 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

hyperclaw-code
Stars16,048195,190
Last commit4mo ago29d ago
LicenseMITMIT
Open issues25541
Has tests
Has CI
Test coverage16%13%
Dependency CVEsNo CVEs0 critical · 0 high · 1 moderate · 0 low
Architecture gradeA
Cycles0
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? hyperium/hyper · ultraworkers/claw-code

Ask AI about hyperium/hyper vs ultraworkers/claw-code

Open the chat with a comparison question pre-filled.