fuellabs/fuel-core vs ogham/exa
Both showing Mixed signals — pick on fit, not health
As of September 2026, fuel-core and exa both show mixed maintenance signals. fuel-core was committed to 1 week ago with 14+ active contributors, while exa last saw a commit 1 year ago with 27+ active contributors. fuel-core has no known critical CVEs, while exa has 2.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
fuellabs/fuel-core
Evidence incomplete — review before adopting
license evidence incomplete
license evidence incomplete
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; license evidence incomplete
- ⚠Scorecard: default branch unprotected (0/10)
- ⚠Could not verify license from the available repository evidence
- ✓Last commit 1d ago
- ✓14 active contributors
- ✓Distributed ownership (top contributor 22% of recent commits)
- ✓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
ogham/exa
Stale — last commit 2y ago
last commit was 2y ago; 2 high-severity CVEs in dependencies…
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
2 high-severity CVEs in dependencies; last commit was 2y ago…
- ⚠Stale — last commit 2y ago
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ⚠2 moderate-severity advisories on direct dependencies
- ⚠2 high-severity advisories in transitive deps
- ✓27+ active contributors
- ✓Distributed ownership (top contributor 41% of recent commits)
- ✓MIT licensed
- ✓CI configured
What would improve this?
- •Use as dependency Mixed to Healthy if: 1 commit in the last 365 days; resolve the high-severity advisories
- •Deploy as-is Concerns to Mixed if: resolve the high-severity advisories
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
| fuel-core | exa | |
|---|---|---|
| Stars | 56,863 | 24,444 |
| Last commit | 11d ago | 1y ago |
| License | Unknown | MIT |
| Open issues | 200 | 213 |
| Has tests | ✓ | No |
| Has CI | ✓ | ✓ |
| Test coverage | 18% | 0% |
| Dependency CVEs | No CVEs | 0 critical · 2 high · 31 moderate · 0 low |
| Architecture grade | A | C |
| Cycles | 0 | 8 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? fuellabs/fuel-core · ogham/exa
Ask AI about fuellabs/fuel-core vs ogham/exa
Open the chat with a comparison question pre-filled.