hashicorp/vault vs smartcontractkit/chainlink
smartcontractkit/chainlink shows stronger signals overall
As of June 2026, chainlink shows healthier maintenance signals than vault. chainlink rates Healthy overall while vault rates Mixed. vault was committed to 1 day ago with 2+ active contributors, while chainlink last saw a commit 1 month ago with 42+ active contributors. Both use the Other license. 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.
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
smartcontractkit/chainlink →
Healthy across the board
non-standard license (Other)
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.
- ⚠Non-standard license (Other) — review terms
- ✓Last commit today
- ✓42+ active contributors
- ✓Distributed ownership (top contributor 12% of recent commits)
- ✓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
Signal-by-signal breakdown
| vault | chainlink | |
|---|---|---|
| Stars | 35,837 | 8,202 |
| Last commit | 1d ago | 1mo ago |
| License | Other | Other |
| Open issues | 1,514 | 300 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 9% | 100% |
| Dependency CVEs | 0 critical · 0 high · 2 moderate · 0 low | No CVEs |
| Architecture grade | C | — |
| Cycles | 0 | — |
| Bottom-line | Mixed signals | Healthy signals |
Want the full analysis? hashicorp/vault · smartcontractkit/chainlink
Ask AI about hashicorp/vault vs smartcontractkit/chainlink
Open the chat with a comparison question pre-filled.