RepoPilot

lapce/lapce vs ogham/exa

lapce/lapce shows stronger signals overall

As of June 2026, lapce shows healthier maintenance signals than exa. lapce rates Healthy overall while exa rates Mixed. lapce last saw a commit 1 month ago with 15+ active contributors, while exa last saw a commit 1 year ago with 27+ active contributors. lapce is Apache-2.0-licensed while exa 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.

lapce/lapce

Healthy

Healthy across the board

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Scorecard: default branch unprotected (0/10)
  • Last commit 1d ago
  • 15 active contributors
  • Distributed ownership (top contributor 45% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

ogham/exa

Mixed

Stale — last commit 2y ago

HealthyDependency

Permissive license, no critical CVEs, actively maintained — safe to depend on.

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

last commit was 2y ago; Scorecard "Branch-Protection" is 0/10…

  • Stale — last commit 2y ago
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • 27+ active contributors
  • Distributed ownership (top contributor 41% of recent commits)
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is MixedHealthy 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

Signal-by-signal breakdown

lapceexa
Stars38,34924,441
Last commit1mo ago1y ago
LicenseApache-2.0MIT
Open issues879213
Has tests
Has CI
Test coverage1%7%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsMixed signals

Want the full analysis? lapce/lapce · ogham/exa

Ask AI about lapce/lapce vs ogham/exa

Open the chat with a comparison question pre-filled.