RepoPilot

data-dog/go-sqlmock vs halfrost/leetcode-go

Both showing Mixed signals — pick on fit, not health

As of September 2026, go-sqlmock and leetcode-go both show mixed maintenance signals. go-sqlmock last saw a commit 2 months ago with 29+ active contributors, while leetcode-go was committed to 2 weeks ago with 8+ active contributors. 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.

data-dog/go-sqlmock

Mixed

Evidence incomplete — review before adopting

MixedDependency

license evidence incomplete

MixedFork & modify

license evidence incomplete

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; license evidence incomplete

  • Scorecard: default branch unprotected (0/10)
  • Could not verify license from the available repository evidence
  • Last commit 8w ago
  • 29+ active contributors
  • Distributed ownership (top contributor 25% of recent commits)
  • CI configured
  • Tests present

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

halfrost/leetcode-go

Mixed

Single-maintainer risk — review before adopting

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

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 Mixed to Healthy 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

go-sqlmockleetcode-go
Stars6,56833,800
Last commit2mo ago14d ago
LicenseUnknownMIT
Open issues442
Has tests
Has CI
Test coverage91%90%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeAA
Cycles00
Bottom-lineMixed signalsMixed signals

Want the full analysis? data-dog/go-sqlmock · halfrost/leetcode-go

Ask AI about data-dog/go-sqlmock vs halfrost/leetcode-go

Open the chat with a comparison question pre-filled.