nautechsystems/nautilus_trader vs yamato-security/hayabusa
Both showing Mixed signals — pick on fit, not health
As of September 2026, nautilus_trader and hayabusa both show mixed maintenance signals. nautilus_trader was committed to 1 week ago with 5+ active contributors, while hayabusa last saw a commit 1 month ago with 4+ active contributors. nautilus_trader is LGPL-3.0-licensed while hayabusa is AGPL-3.0-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.
nautechsystems/nautilus_trader
Single-maintainer risk — review before adopting
copyleft license (LGPL-3.0) — review compatibility; top contributor handles 94% of recent commits
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
No blocking repository-level signals were found; deployment review is still required.
- ⚠Single-maintainer risk — top contributor 94% of recent commits
- ⚠LGPL-3.0 is copyleft — check downstream compatibility
- ✓Last commit today
- ✓5 active contributors
- ✓LGPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Use as dependency Concerns to 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, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard
yamato-security/hayabusa
Mixed signals — read the receipts
copyleft license (AGPL-3.0) — review compatibility; no tests detected in the complete Git tree
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; 8 cyclic import chains — pervasive coupling
- ⚠Small team — 4 contributors active in recent commits
- ⚠Concentrated ownership — top contributor handles 67% of recent commits
- ⚠AGPL-3.0 is copyleft — check downstream compatibility
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 2w ago
- ✓4 active contributors
- ✓AGPL-3.0 licensed
- ✓CI configured
What would improve this?
- •Use as dependency Concerns to Mixed if: relicense under MIT/Apache-2.0 (rare for established libs)
- •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
Signal-by-signal breakdown
| nautilus_trader | hayabusa | |
|---|---|---|
| Stars | 28,330 | 3,311 |
| Last commit | 11d ago | 1mo ago |
| License | LGPL-3.0 | AGPL-3.0 |
| Open issues | 129 | 20 |
| Has tests | ✓ | No |
| Has CI | ✓ | ✓ |
| Test coverage | 14% | 0% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | A | C |
| Cycles | 0 | 8 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? nautechsystems/nautilus_trader · yamato-security/hayabusa
Ask AI about nautechsystems/nautilus_trader vs yamato-security/hayabusa
Open the chat with a comparison question pre-filled.