Registry › Compare › Hindsight vs zvec-grep

Hindsight vs zvec-grep

Both are Grade A and 1.0 points apart, so choose on what you weigh most. Hindsight leads on adoption and rests on broader evidence; zvec-grep leads on supply-chain integrity and transparency. Note: zvec-grep's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types.

A Hindsight 86.4

Hindsight: Agent Memory That Learns

vectorize-io/hindsight · #81 overall · #8 Memory & Knowledge · coverage A (4/5)

Choose Hindsight if adoption matters most.

+3.7Adoption: 19.6k weekly downloads against 3.6k
A vs BEvidence coverage: 4 of 5 independent signal types, against 3

A zvec-grep 87.4

Local-first search across your workspace, built for humans and AI agents.

zvec-ai/zvec-grep · #70 overall · #6 Memory & Knowledge · coverage B (3/5)

Choose zvec-grep if supply-chain integrity and transparency matter most.

+1.0Safety / Integrity: 100% of recent commits signed, against 98%
+0.6Transparency: OSSF Scorecard 5.6 against 4.9

Where they differ

18.5

Safety / Integrityzvec-grep +1.0

19.5

12.7

Transparencyzvec-grep +0.6

13.3

19.9

Maintenancezvec-grep +0.1

20.0

17.2

AdoptionHindsight +3.7

13.5

+0.1

Runtime calibrationzvec-grep +3.0

+3.1

1 dimension identical: Identity 18.0 · Full evidence table

An independent, evidence-based trust comparison of Hindsight and zvec-grep, two Memory & Knowledge projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

Full evidence

Signal	Hindsightvectorize-io/hindsight	zvec-grepzvec-ai/zvec-grep
HVTrust score	86.4	87.4
Evidence grade	A	A
Coverage grade	A	B
Overall rank	#81	#70
Rank in Memory & Knowledge	#8	#6
GitHub stars	58.1k	4.2k
Last updated	1d ago	today
Build provenance	Yes	Yes
OSSF Scorecard	4.9 / 10	5.6 / 10
License	MIT	Apache-2.0
Downloads	20k/wk	4k/wk
Trust dimensions (points earned)
Safety / integrity / 25	18.5	19.5
Identity & provenance / 18	18.0	18.0
Transparency / 17	12.7	13.3
Maintenance / 20	19.9	20.0
Adoption / 20	17.2	13.5
Runtime capability surface (full matrix)
MCP server	Implemented	Declared
External providers	1 — OpenAI	1 — Multi-provider (LiteLLM)
Requires API keys	Yes	No
Plugin surface	plugins	—
Provenance drift	Unknown	Match

Open in the live compare tool → Hindsight profile zvec-grep profile More Memory & Knowledge →

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.4 →