redox-os/orbtk vs ultraworkers/claw-code
ultraworkers/claw-code shows stronger signals overall
As of June 2026, claw-code shows healthier maintenance signals than orbtk. claw-code rates Healthy overall while orbtk rates Mixed. orbtk last saw a commit 3 years 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.
redox-os/orbtk →
Stale — last commit 4y ago
last commit was 4y ago; no tests detected
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 4y ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Stale — last commit 4y ago
- ⚠Single-maintainer risk — top contributor 81% of recent commits
- ⚠No test directory detected
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓6 active contributors
- ✓MIT licensed
- ✓CI configured
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days; 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 OpenSSF Scorecard
ultraworkers/claw-code →
Healthy across the board
Permissive license, no critical CVEs, actively maintained — safe to depend on.
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
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
| orbtk | claw-code | |
|---|---|---|
| Stars | 3,783 | 194,369 |
| Last commit | 3y ago | 1d ago |
| License | MIT | MIT |
| Open issues | 87 | 20 |
| Has tests | — | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 0% | 17% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? redox-os/orbtk · ultraworkers/claw-code
Ask AI about redox-os/orbtk vs ultraworkers/claw-code
Open the chat with a comparison question pre-filled.