halfrost/leetcode-go vs txthinking/brook
Both showing Mixed signals — pick on fit, not health
As of June 2026, leetcode-go and brook both show mixed maintenance signals. leetcode-go was committed to 2 days ago with 8+ active contributors, while brook last saw a commit 4 months ago with 8+ active contributors. leetcode-go is MIT-licensed while brook 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.
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
txthinking/brook →
Single-maintainer risk — review before adopting
copyleft license (GPL-3.0) — review compatibility; top contributor handles 91% of recent commits
Has a license, tests, and CI — clean foundation to fork and modify.
Documented and popular — useful reference codebase to read through.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Single-maintainer risk — top contributor 91% of recent commits
- ⚠GPL-3.0 is copyleft — check downstream compatibility
- ✓Last commit 2mo ago
- ✓8 active contributors
- ✓GPL-3.0 licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed 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
| leetcode-go | brook | |
|---|---|---|
| Stars | 33,785 | 15,115 |
| Last commit | 2d ago | 4mo ago |
| License | MIT | GPL-3.0 |
| Open issues | 5 | 22 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 0% | 1% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | A | — |
| Cycles | 0 | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? halfrost/leetcode-go · txthinking/brook
Ask AI about halfrost/leetcode-go vs txthinking/brook
Open the chat with a comparison question pre-filled.