Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-05 06:34 UTC

alibaba / zvec

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

C++Apache-2.0★ 15,376 stars⑂ 971 forkssince Dec 2025View on GitHub ↗

alibaba/zvec holds a health index of 96 out of 100, placing it in the Exceptional band. It scores highest on Vitality (92/100) and lowest on Security (62/100). It was last updated today. 4 contributors account for most of its recent work.

96
overall / 100
Exceptional

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

96
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 83 is calibrated to 96 on the published index scale (record calibration 2026-08-02).

Ownership

AlibabaOrganization
20,605 followers540 public repossince Jul 2012

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIzvec0.6.040,4731216 days agovector-databaseannnearest-neighbor

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

92Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
22.2/36Commit cadence32/52 weeks with commits
18/18Commit volume338 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year338
human_commit_share0.94
days_since_last_push0
active_weeks_last_year32

Release discipline

100Exceptional
How it's scored
27/27Ships releases10 releases published
36/36Release recencylatest release 16 days ago
27/27Release cadencea release every ~22.3 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count10
latest_release_tagv0.6.0
releases_from_tagsno
days_since_latest_release16
mean_days_between_releases22.3
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

87Excellent · 17% of overall
How it's scored
60/60Stars15,376 stars
24.9/25Forks971 forks
10.3/15Watchers73 watchers
Inputs used
forks971
stars15,376
watchers73
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
61.4/80Monthly downloads40,473 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packageszvec
dependents
ecosystemspypi
total_downloads
monthly_downloads40,473
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

89Excellent · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
18.5/22.5Commit distributiontop contributor authored 18% of commits
13.5/13.5Contributor breadth27 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor4
contributors_sampled27
top_contributor_share0.176
How it's scored
32.7/42Issue resolution78% of issues closed
23.7/30PR acceptance339/430 decided PRs merged
6.5/13Newcomer PR acceptance2/4 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs339
open_issues34
closed_issues119
prs_merged_7d9
prs_decided_7d10
prs_merged_30d44
prs_decided_30d56
issue_closed_ratio0.778
closed_unmerged_prs91
first_time_authors_30d4
first_time_prs_merged_30d2
first_time_prs_decided_30d4
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach20,605 followers of alibaba
25/25Track record540 public repos, account ~14 yr old
Inputs used
followers20,605
owner_typeOrganization
is_verified
owner_loginalibaba
public_repos540
account_age_days5,136
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 16 days ago
20/20Version history12 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageszvec
ecosystemspypi
any_deprecatedno
min_days_since_publish16

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows18 workflow(s)
24/24Tests present
16/16Linter config
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://zvec.org
10/10Repository description
10/10Topics13 topics
10/10Wiki
Inputs used
topicsrag, agent-skills, embedded, faiss, hnsw, llm-memory, search-engine, semantic-search, similarity-search, vector-database, local, db, vector-db
has_wikiyes
homepagehttps://zvec.org
docs_sitehttps://zvec.org
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.2/2.5CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Reviewall changesets reviewed
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowdangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0.5/5SASTSAST tool is not run on all commits -- score normalized to 1
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:zvec@0.6.0 runtime dependency closure — what installing the published package pulls in — 1 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

70Good · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history94 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config
11/11Static type checkingpython/zvec/py.typed
10/10Reproducible environmentDockerfile
10/10Demonstrated agent practice6 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance6 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspython/zvec/py.typed
agent_commit_share0.06
toolchain_manifests
dependency_bot_commit_share0.06
How it's scored
45/45Type-checkable codeC++ (statically typed)
53.3/55Manageable file sizes32/1,066 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes829,414
source_files_sampled1,066
oversized_source_files32
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)src/db/proto/zvec.proto
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filessrc/db/proto/zvec.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

15,376GitHub stars
27contributors
338commits, last 12 months
0days since last push
10releases
4bus factor
34open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • First-time contributor figures cover 12 of 16 authors (cap 12)

More detail

Star and fork history 0 ★ / 971 ⇿
0Stars
971Forks
9Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

02004006008001,000969662026-012026-042026-08
Major 0Minor 5Patch 4
OpenSSF Scorecard 5.3 / 10
5.3aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-05 06:34 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
1SASTSAST tool is not run on all commits -- score normalized to 1
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPInumpy>=1.23pyproject.toml
All dependencies 21

Full resolved dependency set from the GitHub dependency graph: 1 direct and 20 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
PyPInumpydirect
PyPIblackindirect
PyPIbuildindirect
PyPIcibuildwheel3.4.0indirect
PyPIcmakeindirect
PyPImkdocsindirect
PyPImkdocs-materialindirect
PyPImkdocstringsindirect
PyPImypyindirect
PyPIninjaindirect
PyPIpre-commitindirect
PyPIpybind11indirect
PyPIpybind11-stubgenindirect
PyPIpytestindirect
PyPIpytest-covindirect
PyPIpytest-mockindirect
PyPIpytest-xdistindirect
PyPIruffindirect
PyPIscikit-build-coreindirect
PyPIsetuptools-scmindirect
PyPItwineindirect
Dependency advisories 0

Installing pypi:zvec@0.6.0 pulls in 1 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.