RepoPilot

lapce/lapce vs orhun/kmon

lapce/lapce shows stronger signals overall

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

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

orhun/kmon

Mixed

Stale — last commit 1y ago

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility; last commit was 1y ago…

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.

  • Stale — last commit 1y ago
  • GPL-3.0 is copyleft — check downstream compatibility
  • No test directory detected
  • 9 active contributors
  • Distributed ownership (top contributor 39% of recent commits)
  • GPL-3.0 licensed
  • CI configured

What would improve this?

  • Use as dependency ConcernsMixed if: relicense under MIT/Apache-2.0 (rare for established libs)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

Signal-by-signal breakdown

lapcekmon
Stars38,3492,888
Last commit1mo ago1y ago
LicenseApache-2.0GPL-3.0
Open issues87916
Has tests
Has CI
Test coverage1%0%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineHealthy signalsMixed signals

Want the full analysis? lapce/lapce · orhun/kmon

Ask AI about lapce/lapce vs orhun/kmon

Open the chat with a comparison question pre-filled.