RRepoGEO

REPOGEO REPORT · LITE

tensorchord/VectorChord

Default branch main · commit 0768657e · scanned 6/19/2026, 12:21:49 PM

GitHub: 1,702 stars · 64 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface tensorchord/VectorChord, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition README opening to explicitly state relationship to pgvector

    Why:

    CURRENT
    VectorChord (vchord) is a PostgreSQL extension engineered for scalable, high-performance, and cost-effective vector search.
    COPY-PASTE FIX
    VectorChord (vchord) is a high-performance, cost-effective PostgreSQL extension for scalable vector search, designed as a powerful alternative and successor to `pgvector` and `pgvecto.rs` for billion-scale deployments.
  • mediumreadme#2
    Add a dedicated 'Comparison with Alternatives' section to README

    Why:

    COPY-PASTE FIX
    Add a new section titled 'VectorChord vs. Alternatives' or 'Why VectorChord?' that explicitly compares features, performance, and cost against `pgvector`, `Pinecone`, `Milvus`, `Qdrant`, and `Weaviate`.
  • lowreadme#3
    Clarify the project's license directly in the README

    Why:

    COPY-PASTE FIX
    Add a 'License' section or a line in the 'About' section of the README stating: 'VectorChord is licensed under [Specify License Name(s) here, e.g., Apache 2.0 and MIT]. Please see the `LICENSE` file for full details.'

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface tensorchord/VectorChord
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
pgvector
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. pgvector · recommended 1×
  2. Lantern · recommended 1×
  3. TimescaleDB · recommended 1×
  4. ZomboDB · recommended 1×
  5. PostGIS · recommended 1×
  • CATEGORY QUERY
    How to implement scalable and cost-effective vector search directly within PostgreSQL?
    you: not recommended
    AI recommended (in order):
    1. pgvector
    2. Lantern
    3. TimescaleDB
    4. ZomboDB
    5. PostGIS

    AI recommended 5 alternatives but never named tensorchord/VectorChord. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking an alternative to pgvector for high-performance, billion-scale vector search in production.
    you: not recommended
    AI recommended (in order):
    1. Milvus
    2. Pinecone
    3. Qdrant
    4. Weaviate
    5. Elasticsearch
    6. Faiss

    AI recommended 6 alternatives but never named tensorchord/VectorChord. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of tensorchord/VectorChord?
    pass
    AI named tensorchord/VectorChord explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts tensorchord/VectorChord in production, what risks or prerequisites should they evaluate first?
    pass
    AI named tensorchord/VectorChord explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo tensorchord/VectorChord solve, and who is the primary audience?
    pass
    AI named tensorchord/VectorChord explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of tensorchord/VectorChord. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/tensorchord/VectorChord.svg)](https://repogeo.com/en/r/tensorchord/VectorChord)
HTML
<a href="https://repogeo.com/en/r/tensorchord/VectorChord"><img src="https://repogeo.com/badge/tensorchord/VectorChord.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

tensorchord/VectorChord — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite