spieglt/flyingcarpet vs ultraworkers/claw-code
ultraworkers/claw-code shows stronger signals overall
As of June 2026, claw-code shows healthier maintenance signals than flyingcarpet. claw-code rates Healthy overall while flyingcarpet rates Mixed. flyingcarpet last saw a commit 3 months ago with 1+ active contributor, while claw-code was committed to 1 day ago with 10+ active contributors. flyingcarpet is GPL-3.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.
spieglt/flyingcarpet →
Solo project — review before adopting
copyleft license (GPL-3.0) — review compatibility; single-maintainer (no co-maintainers visible)…
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.
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ⚠No CI workflows detected
- ✓Last commit 2mo ago
- ✓GPL-3.0 licensed
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
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
| flyingcarpet | claw-code | |
|---|---|---|
| Stars | 5,156 | 194,369 |
| Last commit | 3mo ago | 1d ago |
| License | GPL-3.0 | MIT |
| Open issues | 21 | 20 |
| Has tests | ✓ | ✓ |
| Has CI | — | ✓ |
| Test coverage | 35% | 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? spieglt/flyingcarpet · ultraworkers/claw-code
Ask AI about spieglt/flyingcarpet vs ultraworkers/claw-code
Open the chat with a comparison question pre-filled.