halfrost/leetcode-go vs opencode-ai/opencode
Both showing Mixed signals — pick on fit, not health
As of September 2026, leetcode-go and opencode both show mixed maintenance signals. leetcode-go was committed to 2 weeks ago with 8+ active contributors, while opencode last saw a commit 12 months ago with 28+ 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
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
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 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
opencode-ai/opencode
Slowing — last commit 11mo ago
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 11mo ago; Scorecard "Branch-Protection" is 0/10
- ⚠Slowing — last commit 11mo ago
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 11mo ago
- ✓28+ active contributors
- ✓Distributed ownership (top contributor 49% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days
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
| leetcode-go | opencode | |
|---|---|---|
| Stars | 33,800 | 13,682 |
| Last commit | 14d ago | 12mo ago |
| License | MIT | MIT |
| Open issues | 2 | 158 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 90% | 3% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 1 moderate · 0 low |
| Architecture grade | A | A |
| Cycles | 0 | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? halfrost/leetcode-go · opencode-ai/opencode
Ask AI about halfrost/leetcode-go vs opencode-ai/opencode
Open the chat with a comparison question pre-filled.