RRepoGEO

REPOGEO REPORT · LITE

CodeSentryAI/lockbud

Default branch main · commit ab1d0951 · scanned 6/16/2026, 11:33:19 AM

GitHub: 591 stars · 39 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 CodeSentryAI/lockbud, 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 introduction to immediately clarify its target language and methodology

    Why:

    CURRENT
    This project, "lockbud", is the artifact of the research paper "Understanding and Detecting Real-World Safety Issues in Rust", published in TSE'24. It builds upon our previous work "Understanding Memory and Thread Safety Practices and Issues in Real-World Rust Programs", published in PLDI'20.
    COPY-PASTE FIX
    lockbud is a static analysis tool specifically designed for Rust projects to detect memory, concurrency bugs, and potential panic locations. It is the artifact of the research paper "Understanding and Detecting Real-World Safety Issues in Rust", published in TSE'24, building upon our previous work "Understanding Memory and Thread Safety Practices and Issues in Real-World Rust Programs", published in PLDI'20.
  • mediumhomepage#2
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    Add a URL to a project page, documentation, or the associated research paper.
  • lowtopics#3
    Expand the repository topics to include more specific bug types

    Why:

    CURRENT
    bug-detection, rust, security, static-analyzer
    COPY-PASTE FIX
    bug-detection, rust, security, static-analyzer, concurrency, memory-safety, panic-detection

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 CodeSentryAI/lockbud
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Miri
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Miri · recommended 2×
  2. Clippy · recommended 1×
  3. KLEE · recommended 1×
  4. Creusot · recommended 1×
  5. RustHorn · recommended 1×
  • CATEGORY QUERY
    How can I statically detect concurrency and memory safety bugs in Rust projects?
    you: not recommended
    AI recommended (in order):
    1. Clippy
    2. Miri
    3. KLEE
    4. Creusot
    5. RustHorn

    AI recommended 5 alternatives but never named CodeSentryAI/lockbud. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools help identify potential panic locations and data races in Rust applications?
    you: not recommended
    AI recommended (in order):
    1. Miri
    2. ThreadSanitizer (TSan)
    3. `loom`
    4. `cargo-udeps`
    5. `clippy`
    6. `cargo-audit`
    7. `cargo-fuzz`

    AI recommended 7 alternatives but never named CodeSentryAI/lockbud. 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 CodeSentryAI/lockbud?
    pass
    AI named CodeSentryAI/lockbud explicitly

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

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

Subscribe to Pro for deep diagnoses

CodeSentryAI/lockbud — 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