cortexlabs/cortex vs hashicorp/vault
Both showing Mixed signals — pick on fit, not health
As of June 2026, cortex and vault both show mixed maintenance signals. cortex last saw a commit 2 years ago with 7+ active contributors, while vault was committed to 1 day ago with 2+ active contributors. cortex is Apache-2.0-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.
cortexlabs/cortex →
Stale — last commit 2y ago
last commit was 2y ago; no CI workflows 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 2y ago; no CI workflows detected
- ⚠Stale — last commit 2y ago
- ⚠Concentrated ownership — top contributor handles 56% of recent commits
- ⚠No CI workflows detected
- ✓7 active contributors
- ✓Apache-2.0 licensed
- ✓Tests present
What would improve this?
- →Use as dependency Mixed → Healthy if: 1 commit in the last 365 days
- →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
| cortex | vault | |
|---|---|---|
| Stars | 8,020 | 35,837 |
| Last commit | 2y ago | 1d ago |
| License | Apache-2.0 | Other |
| Open issues | 131 | 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? cortexlabs/cortex · hashicorp/vault
Ask AI about cortexlabs/cortex vs hashicorp/vault
Open the chat with a comparison question pre-filled.