kaleidawave/ezno vs lapce/lapce
Both showing Healthy signals — pick on fit, not health
As of June 2026, ezno and lapce both show healthy maintenance signals. ezno last saw a commit 3 months ago with 18+ active contributors, while lapce last saw a commit 1 month ago with 15+ active contributors. ezno is MIT-licensed while lapce is Apache-2.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.
kaleidawave/ezno →
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 60% of recent commits
- ✓Last commit 7w ago
- ✓18 active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
lapce/lapce →
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.
- ⚠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
Signal-by-signal breakdown
| ezno | lapce | |
|---|---|---|
| Stars | 2,732 | 38,349 |
| Last commit | 3mo ago | 1mo ago |
| License | MIT | Apache-2.0 |
| Open issues | 46 | 879 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 17% | 1% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | — |
| Cycles | — | — |
| Bottom-line | Healthy signals | Healthy signals |
Want the full analysis? kaleidawave/ezno · lapce/lapce
Ask AI about kaleidawave/ezno vs lapce/lapce
Open the chat with a comparison question pre-filled.