RepoPilot

ultraworkers/claw-code vs ynqa/jnv

ultraworkers/claw-code shows stronger signals overall

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

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

ynqa/jnv

Mixed

Solo project — review before adopting

MixedDependency

single-maintainer (no co-maintainers visible); no tests detected

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.

  • Solo or near-solo (1 contributor active in recent commits)
  • No test directory detected
  • Last commit 5w ago
  • MIT licensed
  • CI configured

What would improve this?

  • Use as dependency MixedHealthy if: onboard a second core maintainer

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

Signal-by-signal breakdown

claw-codejnv
Stars194,3696,007
Last commit1d ago2mo ago
LicenseMITMIT
Open issues2022
Has tests
Has CI
Test coverage17%0%
Dependency CVEs0 critical · 0 high · 1 moderate · 0 lowNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsMixed signals

Want the full analysis? ultraworkers/claw-code · ynqa/jnv

Ask AI about ultraworkers/claw-code vs ynqa/jnv

Open the chat with a comparison question pre-filled.