crawlab-team/crawlab vs hashicorp/vault
Both showing Mixed signals — pick on fit, not health
As of September 2026, crawlab and vault both show mixed maintenance signals. crawlab last saw a commit 7 months ago with 1+ active contributor, while vault was committed to 2 weeks ago with 2+ active contributors. 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.
crawlab-team/crawlab
Slowing — last commit 6mo ago
No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 6mo ago; Scorecard "Token-Permissions" is 0/10
- ⚠Slowing — last commit 6mo ago
- ⚠Solo or near-solo (1 contributor active in recent commits)
- ⚠Scorecard: marked unmaintained (0/10)
- ✓Last commit 6mo ago
- ✓BSD-3-Clause licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days
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
top contributor handles 99% of recent commits; license evidence incomplete
license evidence incomplete
Documented and popular — useful reference codebase to read through.
Scorecard "Token-Permissions" is 0/10; license evidence incomplete
- ⚠Small team — 2 contributors active in recent commits
- ⚠Single-maintainer risk — top contributor 99% of recent commits
- ✓Last commit today
- ✓2 active contributors
- ✓CI configured
- ✓Tests present
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
| crawlab | vault | |
|---|---|---|
| Stars | 12,260 | 36,183 |
| Last commit | 7mo ago | 18d ago |
| License | BSD-3-Clause | Unknown |
| Open issues | 166 | 1,431 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 8% | 51% |
| Dependency CVEs | 0 critical · 0 high · 2 moderate · 0 low | No CVEs |
| Architecture grade | C | — |
| Cycles | 0 | — |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? crawlab-team/crawlab · hashicorp/vault
Ask AI about crawlab-team/crawlab vs hashicorp/vault
Open the chat with a comparison question pre-filled.