RRepoGEO

REPOGEO REPORT · LITE

zzet/gortex

Default branch main · commit 1c29216c · scanned 6/18/2026, 4:36:29 PM

GitHub: 561 stars · 44 forks

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 zzet/gortex, 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 H1/H2 to clearly state AI agent focus and token reduction

    Why:

    CURRENT
    ### Code graph and intelligence engine that indexes repositories
    #### and exposes it via CLI, MCP Server, and web UI.
    COPY-PASTE FIX
    ### Gortex: Local Code Intelligence Engine for AI Agents
    #### Cuts token usage up to 50x by exposing only needed information from your codebase.
  • highabout#2
    Refine 'About' description to emphasize AI agent token optimization and local-first

    Why:

    CURRENT
    High-performance code graph and code intelligence engine, supports 257 languages, multi repositories, with access via CLI, MCP Server, and API. Built for AI coding agents - expose only needed information, cutting token usage up to 50x. 100% local.
    COPY-PASTE FIX
    Gortex is a 100% local code intelligence engine built for AI coding agents. It analyzes 257+ languages across multiple repositories, exposing only needed information via CLI, MCP Server, and API to cut AI token usage up to 50x.
  • mediumreadme#3
    Add a clear differentiator against generic code search/LLM tools in README

    Why:

    COPY-PASTE FIX
    Unlike generic code search tools or LLM frameworks, Gortex is purpose-built for AI coding agents to provide precise, context-aware code intelligence locally, drastically reducing token consumption for AI interactions.

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 zzet/gortex
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
OpenGrok
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. OpenGrok · recommended 2×
  2. Sourcegraph · recommended 2×
  3. LlamaIndex · recommended 1×
  4. LangChain · recommended 1×
  5. Chroma · recommended 1×
  • CATEGORY QUERY
    How can I reduce AI agent token usage when analyzing large codebases locally?
    you: not recommended
    AI recommended (in order):
    1. LlamaIndex
    2. LangChain
    3. Chroma
    4. FAISS
    5. Pinecone
    6. Tree-sitter
    7. tree-sitter-python
    8. tree-sitter-javascript
    9. OpenGrok
    10. Sourcegraph
    11. tokenizers
    12. mistralai/Mistral-7B-Instruct-v0.2
    13. sentence-transformers
    14. all-MiniLM-L6-v2
    15. bge-small-en-v1.5

    AI recommended 15 alternatives but never named zzet/gortex. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools provide a local code intelligence engine for multiple repositories and many languages?
    you: not recommended
    AI recommended (in order):
    1. Sourcegraph
    2. OpenGrok
    3. LSIF
    4. CodeQL
    5. Kite
    6. Ctags

    AI recommended 6 alternatives but never named zzet/gortex. 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 zzet/gortex?
    pass
    AI named zzet/gortex explicitly

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

  • If a team adopts zzet/gortex in production, what risks or prerequisites should they evaluate first?
    pass
    AI named zzet/gortex 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 zzet/gortex solve, and who is the primary audience?
    pass
    AI named zzet/gortex 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 zzet/gortex. 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/zzet/gortex.svg)](https://repogeo.com/en/r/zzet/gortex)
HTML
<a href="https://repogeo.com/en/r/zzet/gortex"><img src="https://repogeo.com/badge/zzet/gortex.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

zzet/gortex — 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