RepoRadar
Leave a Tip
Item detail
github.com

alibaba/zvec

alibaba/zvec is a developer tool that RepoRadar is tracking in its Vector Databases section, currently rated Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.5 out of 10.

Open on GitHub →Back to radar
Score8.4
Popularity95.0
Risknone
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum9.0
Maturity8.5
Open-source/build8.4
Evidence7.2
Workflow potential9.5
Setup ease8.8

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for developers building local-first RAG or agent-memory apps who do not want to stand up a vector server: pip install zvec, open a collection in-process, and run dense-vector, sparse-vector, full-text, or hybrid MultiQuery against it from Python, Node, Go, or Rust without an external process. The DiskANN index means the same library now scales to collections that exceed RAM.

Who should use it

developers building local-first RAG or agent-memory apps who do not want to run a separate vector server teams that want dense + sparse + full-text + scalar-filter queries in one library instead of stitching FAISS + a search engine Go and Rust users who finally have a first-party vector-DB SDK without an HTTP client wrapper projects whose collections exceed RAM and need an on-disk index (DiskANN in v0.5) without switching to a server stack Alibaba / China-cloud users who want a vector DB built and battle-tested in the same ecosystem

Who should skip it

Skip alibaba/zvec unless the captured evidence suggests it solves a problem you are actively working on.

About this signal

alibaba/zvec is tracked by RepoRadar as a developer tool in the Vector Databases section. First seen 2026-06-17; the source record was last checked on 2026-06-17. The current verdict is 'try now' with a Gold tier and easy setup difficulty. alibaba/zvec leads on workflow potential (9.5) and momentum (9.0); its lowest signal is evidence quality (7.2), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The alibaba/zvec record combines a 8.4/10 composite score with separate popularity (95.0), risk (none), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links
Closest alternatives / related signals
vector-database embedded in-process alibaba similarity-search full-text-search hybrid-search diskann
Verification record

What RepoRadar actually verified

Tested in a bounded workflow

Bounded representative workflow retained by RepoRadar verification harness. Last checked 2026-07-13T10:36:46.807451Z.

passed · cohort-20260712-zvec-local-vector-collection-workflow

Tester
RepoRadar automated local verification harness
Started
2026-07-13T10:36:43.119028Z
Completed
2026-07-13T10:36:46.807451Z
Environment
Windows 10 AMD64; Python 3.11.9; credential-stripped child environment; disposable home/cache
Install/setup time
1 minute(s)
Evidence scope
Bounded representative workflow
Cleanup
Per-check temporary home and work directory removed. Shared cohort package cache removed.
Actions exercised
  • Created a disposable home, work directory, and isolated package cache with credential-like environment variables excluded.
  • Created 1 synthetic fixture file(s) inside the disposable work directory; retained hashes prove the exact inputs.
  • Defined a local Zvec schema with one scalar field and a two-dimensional flat vector index, then inserted three runbook records.
  • Queried with a supplied incident vector, asserted rollback ranked first with platform metadata, and retained the ranked results.
  • Executed bounded check: Create a persistent local Zvec collection, insert supplied vectors, and retrieve the expected runbook.
  • Captured the complete sanitized stdout, stderr, exit status, artifact checks, and 3.69-second wall time.
Observed results
  • Command exited 0 after 3.69 seconds.
  • Zvec persisted three records and returned rollback first with its platform field intact.
  • Expected marker 'CHECK_OK top=rollback team=platform count=3' was observed in retained output.
  • Validated result.json: 3 required marker(s) present and 0 excluded marker(s) absent; size and SHA-256 are retained.
Observed strengths
  • The embedded collection completed schema creation, persistence, insert, vector query, and scalar-field return with no server process.
Friction
  • The workflow requires explicit vector dimension, index type, supplied embeddings, and local store lifecycle management.
  • Setup or runtime emitted 3 stderr line(s); the complete warnings/errors are preserved in the retained log.
Limitations
  • The flat two-dimensional fixture validates local collection CRUD and vector search, not embeddings, large indexes, filters, concurrency, or production recall and latency.
  • This credential-free disposable workflow does not establish production scale, model quality, reliability under sustained use, or team adoption.

Pricing assessment: The embedded Zvec collection ran locally with caller-supplied vectors and no cloud database or embedding-model charge.

Privacy assessment: Synthetic records and vectors were written only to the disposable Zvec store, which the harness removed after hashing proof output.

Open retained test log →

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

48 dated snapshots retained from 2026-06-17 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.4 current · +0.0 net
Repository momentum9.3 current · +0.3 net
GitHub stars (observed)15,437 current · +569 net
GitHub stars15,437 exact observation
Versionv0.6.0
Last release2026-07-20T06:06:19Z
Maintenanceactive
Current risknone
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.49.315,437nonetry nowactive
2026-08-128.49.315,431nonetry nowactive
2026-08-118.49.315,420nonetry nowactive
2026-08-108.49.315,411nonetry nowactive
2026-08-098.49.315,409nonetry nowactive
2026-08-088.49.315,405nonetry nowactive
2026-08-078.49.315,365nonetry nowactive
2026-08-068.49.0Not recordednonetry nownot recorded
2026-08-058.49.0Not recordednonetry nownot recorded
2026-08-048.49.315,365nonetry nowactive
2026-08-038.49.315,365nonetry nowactive
2026-08-028.49.315,355nonetry nowactive

Why the record changed

stars changed

Stars changed: 15431 → 15437.

stars changed

Stars changed: 15420 → 15431.

stars changed

Stars changed: 15411 → 15420.

stars changed

Stars changed: 15409 → 15411.

stars changed

Stars changed: 15405 → 15409.

stars changed

Stars changed: 15365 → 15405.

stars changed

Stars changed: 15355 → 15365.

stars changed

Stars changed: 15351 → 15355.

stars changed

Source-observed stars changed: 15346 → 15351. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 15294 → 15306.

stars changed

Source-observed stars changed: 15291 → 15294. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed

Version changed: v0.5.1 → v0.6.0.