ogham/exa vs sharkdp/bat
sharkdp/bat shows stronger signals overall
As of September 2026, bat shows healthier maintenance signals than exa. bat rates Healthy overall while exa rates Mixed. exa last saw a commit 1 year ago with 27+ active contributors, while bat was committed to 1 week ago with 18+ active contributors. exa is MIT-licensed while bat is Apache-2.0-licensed. bat 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.
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
sharkdp/bat
Strong maintenance signals
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Token-Permissions" is 0/10; 1 cyclic import chain detected
- ⚠1 moderate-severity advisory on direct dependencies
- ✓Last commit 2d ago
- ✓18 active contributors
- ✓Distributed ownership (top contributor 28% of recent commits)
- ✓Apache-2.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Token-Permissions" 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
| exa | bat | |
|---|---|---|
| Stars | 24,444 | 60,380 |
| Last commit | 1y ago | 12d ago |
| License | MIT | Apache-2.0 |
| Open issues | 213 | 426 |
| Has tests | No | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 0% | 100% |
| Dependency CVEs | 0 critical · 2 high · 31 moderate · 0 low | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | C | A |
| Cycles | 8 | 1 |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? ogham/exa · sharkdp/bat
Ask AI about ogham/exa vs sharkdp/bat
Open the chat with a comparison question pre-filled.