halfrost/leetcode-go vs jmoiron/sqlx
Both showing Mixed signals — pick on fit, not health
As of June 2026, leetcode-go and sqlx both show mixed maintenance signals. leetcode-go was committed to 2 days ago with 8+ active contributors, while sqlx last saw a commit 1 year ago with 29+ 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.
halfrost/leetcode-go →
Single-maintainer risk — review before adopting
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.
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 → 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
jmoiron/sqlx →
Stale — last commit 2y ago
last commit was 2y ago; no tests detected…
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; no CI workflows detected
- ⚠Stale — last commit 2y ago
- ⚠Concentrated ownership — top contributor handles 57% of recent commits
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓29+ active contributors
- ✓MIT licensed
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days; add a test suite
- →Deploy as-is Mixed → Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
Signal-by-signal breakdown
| leetcode-go | sqlx | |
|---|---|---|
| Stars | 33,785 | 17,619 |
| Last commit | 2d ago | 1y ago |
| License | MIT | MIT |
| Open issues | 5 | 386 |
| Has tests | ✓ | — |
| Has CI | ✓ | — |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | A | — |
| Cycles | 0 | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? halfrost/leetcode-go · jmoiron/sqlx
Ask AI about halfrost/leetcode-go vs jmoiron/sqlx
Open the chat with a comparison question pre-filled.