RepoPilot

codislabs/codis vs halfrost/leetcode-go

Both showing Mixed signals — pick on fit, not health

As of June 2026, codis and leetcode-go both show mixed maintenance signals. codis last saw a commit 2 years ago with 16+ active contributors, while leetcode-go was committed to 2 days ago with 8+ active contributors. Both use the MIT license. 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.

codislabs/codis

Mixed

Stale — last commit 2y ago

MixedDependency

last commit was 2y ago; no tests detected

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 2y ago
  • Concentrated ownership — top contributor handles 68% of recent commits
  • No test directory detected
  • 16 active contributors
  • MIT licensed
  • CI configured

What would improve this?

  • Use as dependency MixedHealthy if: 1 commit in the last 365 days

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

halfrost/leetcode-go

Mixed

Single-maintainer risk — review before adopting

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

Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10

  • Single-maintainer risk — top contributor 93% of recent commits
  • Scorecard: default branch unprotected (0/10)
  • Last commit 1d ago
  • 8 active contributors
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is MixedHealthy if: 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 dependency CVEs from deps.dev and OpenSSF Scorecard

Signal-by-signal breakdown

codisleetcode-go
Stars13,23333,785
Last commit2y ago2d ago
LicenseMITMIT
Open issues3055
Has tests
Has CI
Test coverage0%0%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeA
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? codislabs/codis · halfrost/leetcode-go

Ask AI about codislabs/codis vs halfrost/leetcode-go

Open the chat with a comparison question pre-filled.