Zvec has an HVTrust score of 64.1/100 (Grade C), ranked #231 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Zvec?

Zvec scores 64.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 15.4k GitHub stars and is categorized under Memory & Knowledge.

Zvec

alibaba/zvec

A lightweight, lightning-fast, in-process vector database

Memory & Knowledge C++ Grade C Listed Apache-2.0

64.1/100

Rank #231 of 1204

Compare Zvec

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade A · 4/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Provider Added +2

Is Zvec safe? Zvec scores 64.1/100 (Grade C), ranked #231 of 1204 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.3/10; 100% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Memory & Knowledge

#19 Vellum Assistant — 67.7 (B) → #20 agentmemory — 67.4 (B) → #22 WeKnora — 61.5 (C) → #23 Beads — 61.4 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-08-08

Rank Moved

Rank dropped 47 spots (#173 → #220)

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.3/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Zvec View Memory & Knowledge Report missing data

83.7

Activity sub-score · out of 100

#21

In Memory & Knowledge

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 →

Activity & Reach

Stars

15.4k

Forks

973

Last Push

2026-08-09

today

Commits (4 wk)

Downloads (7d)

15,850

npm+pypi

HN mentions (30d)

Open Issues

Rank Change

▼11

was #220

Analysis

HVTrust Dimensions vs Memory & Knowledge

64.1 / 100 · 100.0% confidence

Zvec Memory & Knowledge average (38 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.6 / 25

1.0 above avg 10.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.5 below avg 12.3

Transparency50% declared license · 50% OSSF Scorecard

13.0 / 17

in line with avg 12.7

Maintenance60% last-push freshness · 40% commit activity

18.3 / 20

0.8 above avg 17.5

AdoptionLog-scaled stars · package downloads

15.7 / 20

1.6 above avg 14.1

Activity Inputs

83.7 / 100

StarsRepository reach

25.1 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

19.7 / 25

CommunityFork signal

13.9 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Aug 8, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 9

CII-Best-Practices 0

Code-Review 10

Contributors 6

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 0

SAST 1

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Is Zvec safe?

Zvec has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Zvec publish package provenance?

No published build provenance is currently detected for Zvec. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Zvec have an OpenSSF Scorecard?

Zvec has an OpenSSF Scorecard score of 5.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Zvec actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Zvec use?

Zvec ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Zvec's commits signed?

100% of the last 100 commits to Zvec are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Postgres

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

database

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Warning

1 package source mismatch detected

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

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.

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres

2026-07-17

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-09

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-08-08

Rank Moved

Rank dropped 47 spots (#173 → #220)

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Postgres

2026-07-17

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-07-14

Rank Moved

Rank dropped 13 spots (#145 → #158)

2026-07-13

Rank Moved

Rank dropped 14 spots (#131 → #145)

2026-06-18

Scorecard Added

OSSF Scorecard: 5.2/10

2026-06-18

Grade Changed

Trust grade D → B

2026-06-18

Rank Moved

Rank rose 85 spots (#173 → #88)

2026-06-18

HVTrust Changed

HVTrust up 25.5pts (43.6 → 69.1)

2026-06-17

Newly Listed

First tracked at rank #173

GitHub → PyPI: zvec npm: @zvec/zvec

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/zvec.svg)](https://hvtracker.net/agents/zvec)
            
HTML:
            <a href="https://hvtracker.net/agents/zvec"><img src="https://hvtracker.net/badge/zvec.svg" alt="HVTrust"></a>

Other agents in Memory & Knowledge

Data sources
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.2 · Raw JSON