RepoPilot

gopeedlab/gopeed vs hashicorp/vault

Both showing Mixed signals — pick on fit, not health

As of June 2026, gopeed and vault both show mixed maintenance signals. gopeed last saw a commit 1 month ago with 21+ active contributors, while vault was committed to today with 2+ active contributors. gopeed is GPL-3.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.

gopeedlab/gopeed

Mixed

Mixed signals — read the receipts

ConcernsDependency

copyleft license (GPL-3.0) — review compatibility

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No critical CVEs, sane security posture — runnable as-is.

  • Concentrated ownership — top contributor handles 57% of recent commits
  • GPL-3.0 is copyleft — check downstream compatibility
  • Last commit 2d ago
  • 21+ active contributors
  • GPL-3.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency ConcernsMixed if: relicense under MIT/Apache-2.0 (rare for established libs)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

hashicorp/vault

Mixed

Single-maintainer risk — review before adopting

ConcernsDependency

non-standard license (Other); top contributor handles 99% of recent commits

HealthyFork & modify

Has a license, tests, and CI — clean foundation to fork and modify.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

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 ConcernsMixed 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

gopeedvault
Stars24,37735,837
Last commit1mo agotoday
LicenseGPL-3.0Other
Open issues2731,514
Has tests
Has CI
Test coverage48%9%
Dependency CVEsNo CVEs0 critical · 0 high · 2 moderate · 0 low
Architecture gradeC
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? gopeedlab/gopeed · hashicorp/vault

Ask AI about gopeedlab/gopeed vs hashicorp/vault

Open the chat with a comparison question pre-filled.