RepoPilot

halfrost/halfrost-field vs hashicorp/vault

Both showing Mixed signals — pick on fit, not health

As of September 2026, halfrost-field and vault both show mixed maintenance signals. halfrost-field last saw a commit 2 years ago with 4+ 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.

halfrost/halfrost-field

Mixed

Stale — last commit 2y ago

ConcernsDependency

non-standard license (CC-BY-SA-4.0); last commit was 2y ago…

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 2y ago; dependency CVE scan unavailable

  • Stale — last commit 2y ago
  • Small team — 4 contributors active in recent commits
  • Single-maintainer risk — top contributor 97% of recent commits
  • Non-standard license (CC-BY-SA-4.0) — review terms
  • 4 active contributors
  • CC-BY-SA-4.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Use as dependency Concerns to Mixed if: clarify license terms

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

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

halfrost-fieldvault
Stars13,21336,183
Last commit2y ago16d ago
LicenseCC-BY-SA-4.0Unknown
Open issues31,431
Has tests
Has CI
Test coverage100%51%
Dependency CVEsNo CVEsNo CVEs
Architecture grade
Cycles
Bottom-lineMixed signalsMixed signals

Want the full analysis? halfrost/halfrost-field · hashicorp/vault

Ask AI about halfrost/halfrost-field vs hashicorp/vault

Open the chat with a comparison question pre-filled.