RRepoGEO

REPOGEO REPORT · LITE

probelabs/probe

Default branch main · commit 53ed5860 · scanned 6/1/2026, 11:41:15 PM

GitHub: 625 stars · 62 forks

AI VISIBILITY SCORE
33 /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
2 / 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 probelabs/probe, 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 the README's opening paragraph to clarify its core purpose for AI assistants

    Why:

    CURRENT
    We read code 10x more than we write it. Probe is a code and markdown context engine, with a built-in agent, made to work on enterprise-scale codebases.
    COPY-PASTE FIX
    Probe is an AI-friendly semantic code search engine for large codebases. It combines ripgrep speed with tree-sitter AST parsing to power AI coding assistants with precise, context-aware code understanding. We read code 10x more than we write it. Probe is a code and markdown context engine, with a built-in agent, made to work on enterprise-scale codebases.
  • mediumtopics#2
    Add more specific topics related to AI assistant integration and RAG for code

    Why:

    CURRENT
    ai, ai-coder, ast, cli, code-search, mcp, nodejs-sdk, ripgrep, rust, search-engine, semantic-search, tree-sitter
    COPY-PASTE FIX
    ai, ai-coder, ast, cli, code-search, mcp, nodejs-sdk, ripgrep, rust, search-engine, semantic-search, tree-sitter, ai-assistants, rag-for-code, llm-tools, code-intelligence
  • lowreadme#3
    Add a 'Comparison' section to the README to differentiate from alternatives

    Why:

    COPY-PASTE FIX
    Add a new top-level section to the README, e.g., '## Probe vs. Alternatives', explaining how Probe specifically differs from and complements tools like Sourcegraph, Semgrep, and general ML models for code understanding in AI contexts.

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 probelabs/probe
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. Faiss · recommended 1×
  4. Sentence Transformers · recommended 1×
  5. CodeBERT · recommended 1×
  • CATEGORY QUERY
    How to find relevant code snippets semantically across a massive codebase for AI assistants?
    you: not recommended
    AI recommended (in order):
    1. Faiss
    2. Sentence Transformers
    3. CodeBERT
    4. GraphCodeBERT
    5. UniXcoder
    6. OpenAI Embeddings
    7. Weaviate
    8. Qdrant
    9. Pinecone
    10. Elasticsearch
    11. OpenGrok
    12. Sourcegraph
    13. Annoy

    AI recommended 13 alternatives but never named probelabs/probe. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a code search tool that understands AST for better context than grep.
    you: not recommended
    AI recommended (in order):
    1. Sourcegraph
    2. Semgrep
    3. Comby
    4. OpenGrok
    5. CodeQL
    6. Tree-sitter CLI

    AI recommended 6 alternatives but never named probelabs/probe. 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 probelabs/probe?
    pass
    AI did not name probelabs/probe — likely talking about a different project

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

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

Subscribe to Pro for deep diagnoses

probelabs/probe — 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