go-kit/kit vs hashicorp/vault
go-kit/kit shows stronger signals overall
As of June 2026, kit shows healthier maintenance signals than vault. kit rates Healthy overall while vault rates Mixed. kit last saw a commit 1 year ago with 26+ active contributors, while vault was committed to 1 day ago with 2+ active contributors. kit 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.
go-kit/kit →
Healthy across all four use cases
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.
No critical CVEs, sane security posture — runnable as-is.
- ⚠Stale — last commit 2y ago
- ⚠Concentrated ownership — top contributor handles 51% of recent commits
- ✓26+ active contributors
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests
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
| kit | vault | |
|---|---|---|
| Stars | 27,426 | 35,837 |
| Last commit | 1y ago | 1d ago |
| License | MIT | Other |
| Open issues | 58 | 1,514 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 4% | 9% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 2 moderate · 0 low |
| Architecture grade | — | C |
| Cycles | — | 0 |
| Bottom-line | Healthy signals | Mixed signals |
Want the full analysis? go-kit/kit · hashicorp/vault
Ask AI about go-kit/kit vs hashicorp/vault
Open the chat with a comparison question pre-filled.