RepoPilot

hashicorp/vault vs wei-shaw/sub2api

Both showing Mixed signals — pick on fit, not health

As of September 2026, vault and sub2api both show mixed maintenance signals. vault was committed to 2 weeks ago with 2+ active contributors, while sub2api was committed to 1 week ago with 20+ 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

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

wei-shaw/sub2api

Mixed

Mixed signals — read the receipts

ConcernsDependency

copyleft license (LGPL-3.0) — review compatibility

HealthyFork & modify

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

HealthyLearn from

Documented and popular — useful reference codebase to read through.

HealthyDeploy as-is

No blocking repository-level signals were found; deployment review is still required.

  • Concentrated ownership — top contributor handles 50% of recent commits
  • LGPL-3.0 is copyleft — check downstream compatibility
  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 20 active contributors
  • LGPL-3.0 licensed
  • CI configured
  • Tests present

What would improve this?

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

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

vaultsub2api
Stars36,18340,594
Last commit19d ago10d ago
LicenseUnknownLGPL-3.0
Open issues1,4313,080
Has tests
Has CI
Test coverage51%100%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeC
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? hashicorp/vault · wei-shaw/sub2api

Ask AI about hashicorp/vault vs wei-shaw/sub2api

Open the chat with a comparison question pre-filled.