RRepoGEO

REPOGEO REPORT · LITE

gersteinlab/LocAgent

Default branch master · commit ef170542 · scanned 6/1/2026, 2:38:04 PM

GitHub: 611 stars · 93 forks

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 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 gersteinlab/LocAgent, 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
    Clarify the README's opening sentence to explicitly state the software domain

    Why:

    CURRENT
    We introduce **LocAgent**, a framework that addresses code localization through graph-based representation.
    COPY-PASTE FIX
    We introduce **LocAgent**, a graph-guided agentic framework specifically designed for **software code localization** within complex software projects, as presented at ACL 2025.
  • hightopics#2
    Add specific topics to improve categorization and search

    Why:

    CURRENT
    (none)
    COPY-PASTE FIX
    llm-agents, code-localization, graph-neural-networks, code-analysis, software-engineering, large-language-models, acl-2025
  • mediumhomepage#3
    Add the paper link to the repository homepage field

    Why:

    COPY-PASTE FIX
    https://arxiv.org/abs/2503.09089

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 gersteinlab/LocAgent
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GitHub Copilot Chat
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. GitHub Copilot Chat · recommended 1×
  2. Cursor · recommended 1×
  3. Sourcegraph Cody · recommended 1×
  4. Tabnine · recommended 1×
  5. Codeium · recommended 1×
  • CATEGORY QUERY
    How to improve code understanding and navigation in complex software projects using AI?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot Chat
    2. Cursor
    3. Sourcegraph Cody
    4. Tabnine
    5. Codeium
    6. OpenAI's GPT-4
    7. ChatGPT Enterprise
    8. Google Gemini
    9. Bard/Gemini Advanced

    AI recommended 9 alternatives but never named gersteinlab/LocAgent. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What frameworks leverage large language models and graph representations for source code analysis?
    you: not recommended
    AI recommended (in order):
    1. CodeQL
    2. Semgrep
    3. GraphCodeBERT
    4. CodeBERT
    5. UniXcoder
    6. DeepCode
    7. Snyk Code
    8. PyTorch Geometric (PyG)
    9. Deep Graph Library (DGL)
    10. Hugging Face Transformers
    11. GPT-Neo
    12. Llama

    AI recommended 12 alternatives but never named gersteinlab/LocAgent. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    warn

    Suggestion:

  • 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 gersteinlab/LocAgent?
    pass
    AI named gersteinlab/LocAgent explicitly

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

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

Subscribe to Pro for deep diagnoses

gersteinlab/LocAgent — 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