halfrost/leetcode-go vs hashicorp/vault
Both showing Mixed signals — pick on fit, not health
As of June 2026, leetcode-go and vault both show mixed maintenance signals. leetcode-go was committed to 2 days ago with 8+ active contributors, while vault was committed to today with 2+ active contributors. leetcode-go is MIT-licensed while vault is Other-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
hashicorp/vault →
Single-maintainer risk — review before adopting
non-standard license (Other); top contributor handles 99% 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.
- ⚠Small team — 2 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 99% of recent commits
- ⚠Non-standard license (Other) — review terms
- ⚠2 moderate-severity advisories on direct dependencies
- ✓Last commit today
- ✓2 active contributors
- ✓Other licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- →Use as dependency Concerns → Mixed if: clarify license terms
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 | vault | |
|---|---|---|
| Stars | 33,785 | 35,837 |
| Last commit | 2d ago | today |
| License | MIT | Other |
| Open issues | 5 | 1,514 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 0% | 9% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 2 moderate · 0 low |
| Architecture grade | A | C |
| Cycles | 0 | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? halfrost/leetcode-go · hashicorp/vault
Ask AI about halfrost/leetcode-go vs hashicorp/vault
Open the chat with a comparison question pre-filled.