RepoPilot

google/wire vs hashicorp/vault

Both showing Mixed signals — pick on fit, not health

As of September 2026, wire and vault both show mixed maintenance signals. wire last saw a commit 1 year ago with 26+ active contributors, 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.

google/wire

Mixed

Stale — last commit 1y ago

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

last commit was 1y ago; Scorecard "Token-Permissions" is 0/10

  • Stale — last commit 1y ago
  • Scorecard: marked unmaintained (0/10)
  • 26+ active contributors
  • Distributed ownership (top contributor 36% of recent commits)
  • Apache-2.0 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

Mixed

Single-maintainer risk — review before adopting

MixedDependency

top contributor handles 99% of recent commits; license evidence incomplete

MixedFork & modify

license evidence incomplete

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

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

wirevault
Stars14,40836,183
Last commit1y ago19d ago
LicenseApache-2.0Unknown
Open issues1081,431
Has tests
Has CI
Test coverage0%51%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeB
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? google/wire · hashicorp/vault

Ask AI about google/wire vs hashicorp/vault

Open the chat with a comparison question pre-filled.