gorilla/websocket vs hashicorp/vault
Both showing Mixed signals — pick on fit, not health
As of June 2026, websocket and vault both show mixed maintenance signals. websocket last saw a commit 1 year ago with 47+ active contributors, while vault was committed to today with 2+ active contributors. websocket is BSD-2-Clause-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.
gorilla/websocket →
Stale — last commit 1y ago
last commit was 1y 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 1y ago; no CI workflows detected
- ⚠Stale — last commit 1y ago
- ⚠No CI workflows detected
- ⚠No test directory detected
- ✓47+ active contributors
- ✓Distributed ownership (top contributor 9% of recent commits)
- ✓BSD-2-Clause 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
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
| websocket | vault | |
|---|---|---|
| Stars | 24,688 | 35,837 |
| Last commit | 1y ago | today |
| License | BSD-2-Clause | Other |
| Open issues | 73 | 1,514 |
| Has tests | — | ✓ |
| Has CI | — | ✓ |
| Test coverage | 0% | 9% |
| Dependency CVEs | No CVEs | 0 critical · 0 high · 2 moderate · 0 low |
| Architecture grade | — | C |
| Cycles | — | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? gorilla/websocket · hashicorp/vault
Ask AI about gorilla/websocket vs hashicorp/vault
Open the chat with a comparison question pre-filled.