hashicorp/vault vs usefathom/fathom
Both showing Mixed signals — pick on fit, not health
As of September 2026, vault and fathom both show mixed maintenance signals. vault was committed to 2 weeks ago with 2+ active contributors, while fathom last saw a commit 6 months ago with 15+ 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.
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
usefathom/fathom
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.
Scorecard "Branch-Protection" is 0/10; Scorecard "Token-Permissions" is 0/10
- ⚠Slowing — last commit 6mo ago
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 6mo ago
- ✓15 active contributors
- ✓Distributed ownership (top contributor 49% of recent commits)
- ✓MIT licensed
- ✓CI configured
- ✓Tests present
What would improve this?
- •Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)
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
| vault | fathom | |
|---|---|---|
| Stars | 36,183 | 8,018 |
| Last commit | 19d ago | 6mo ago |
| License | Unknown | MIT |
| Open issues | 1,431 | 5 |
| Has tests | ✓ | ✓ |
| Has CI | ✓ | ✓ |
| Test coverage | 51% | 20% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | — | A |
| Cycles | — | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? hashicorp/vault · usefathom/fathom
Ask AI about hashicorp/vault vs usefathom/fathom
Open the chat with a comparison question pre-filled.