Zvec
Website
A lightweight, lightning-fast, in-process vector database
Is Zvec safe? Promising trust profile, but some evidence still deserves review.
Compare Zvec
How does it stack up against its Memory & Knowledge neighbours?
Pick any agent to compare →In detail: Zvec scores 63.2/100 (Grade C), ranked #595 of 1374 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 100% of recent commits are signed; no published advisory affects its latest release (zvec); last pushed 2026-10-30. Every point is earned from checkable signals — never paid placement. How scoring works →
How Zvec could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesnpm publish --provenance from CI +14.8 → 78.0 B · #12 of 50
- Raise the OSSF Scorecard from 5.0 to 9.0lowest checks: CII-Best-Practices 0, Dangerous-Workflow 0, Fuzzing 0 +8.3 → 71.5 B · #21 of 50
Chain of custody
Scanners check what the code says. This traces who ships Zvec and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/alibaba/zvec, Apache-2.0, last pushed 2026-10-30. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.0/10 (scanned Oct 30, 2026). The checks that decide who can get a change released:
- Code Review10
- Branch Protection6
- Signed Releases0
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 6CI-Tests 9CII-Best-Practices 0Code-Review 10Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 0SAST 1Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 10 -
Published packages Source mismatch
- npm @zvec/zvec Source link points to zvec-ai/zvec-node, not this repo No build attestation
- PyPI zvec Source link points back to this repo No build attestation
A package whose source link names another repository may belong to a different project, or the project may have moved. HVTracker treats it as a mismatch until that is confirmed. Know which? Suggest a correction
-
What you install today No known advisories
Latest release checked: zvec 0.8.0. No published advisory affects it (OSV, checked 2026-10-30).
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Zvec.
Evidence behind this score
Coverage A: 4 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues Zvec’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Zvec compares in Memory & Knowledge
- #32 Chroma 64.9 +1.7
- #33 Beads 64.2 +1.0
- #34 Zvec 63.2 this agent
- #35 AnythingLLM 62.3 −0.9
- #36 PrivateGPT 59.9 −3.3
Bars show each HVTrust score; the tick marks Zvec’s 63.2.
Where the 63.2 comes from
HVTrust dimensions vs the Memory & Knowledge average
63.2 / 100 · 100.0% confidenceZvec Memory & Knowledge average (50 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
82.3 / 100Common questions about Zvec
Does Zvec publish package provenance?
Does Zvec have an OpenSSF Scorecard?
Is Zvec actively maintained?
What license does Zvec use?
Are Zvec's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Zvec's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Zvec?
For maintainers
HVTrust scores Zvec from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/zvec)
<a href="https://hvtracker.net/agents/zvec"><img src="https://hvtracker.net/badge/zvec.svg" alt="HVTrust"></a>
Other agents in Memory & Knowledge
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON