RepoPilot

disintegration/imaging vs hashicorp/vault

Both showing Mixed signals — pick on fit, not health

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

disintegration/imaging

Mixed

Stale — last commit 3y 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 3y ago; Scorecard "Branch-Protection" is 0/10

  • Stale — last commit 3y ago
  • Concentrated ownership — top contributor handles 65% of recent commits
  • Scorecard: marked unmaintained (0/10)
  • Scorecard: default branch unprotected (0/10)
  • 13 active contributors
  • MIT 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

imagingvault
Stars5,75636,183
Last commit2y ago18d ago
LicenseMITUnknown
Open issues351,431
Has tests
Has CI
Test coverage100%51%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeA
Cycles0
Bottom-lineMixed signalsMixed signals

Want the full analysis? disintegration/imaging · hashicorp/vault

Ask AI about disintegration/imaging vs hashicorp/vault

Open the chat with a comparison question pre-filled.