RRepoGEO

REPOGEO REPORT · LITE

liveloveapp/hashbrown

Default branch main · commit c33abf4f · scanned 6/8/2026, 9:47:51 AM

GitHub: 705 stars · 63 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 liveloveapp/hashbrown, 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
    Add a disambiguation note to the README's introduction

    Why:

    COPY-PASTE FIX
    Add a short, clear sentence immediately after the main title or opening paragraph, for example: "Note: This project is a JavaScript/TypeScript framework for building browser agents, and is unrelated to the Rust `hashbrown` crate."
  • mediumtopics#2
    Expand topics to emphasize browser-based AI agents

    Why:

    CURRENT
    ai, angular, llms, react, typescript, ui, ux
    COPY-PASTE FIX
    ai, angular, llms, react, typescript, ui, ux, browser-agents, frontend-ai, web-agents, agent-framework, llm-agents
  • mediumlicense#3
    Clarify the existing license in the README

    Why:

    COPY-PASTE FIX
    Add a section to the README, for example: "## License\nThis project is licensed under a custom license. Please see the [LICENSE](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 liveloveapp/hashbrown
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Playwright
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Playwright · recommended 1×
  2. Puppeteer · recommended 1×
  3. Selenium WebDriver · recommended 1×
  4. Cypress · recommended 1×
  5. Robot Framework · recommended 1×
  • CATEGORY QUERY
    Framework for building AI agents that interact with browser UI, supporting React/Angular?
    you: not recommended
    AI recommended (in order):
    1. Playwright
    2. Puppeteer
    3. Selenium WebDriver
    4. Cypress
    5. Robot Framework

    AI recommended 5 alternatives but never named liveloveapp/hashbrown. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How to develop LLM-powered agents that operate directly within a web application frontend?
    you: not recommended
    AI recommended (in order):
    1. LangChain.js
    2. LlamaIndex.TS
    3. OpenAI API
    4. Hugging Face Transformers.js
    5. WebLLM
    6. MLC LLM

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

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

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

Subscribe to Pro for deep diagnoses

liveloveapp/hashbrown — 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
liveloveapp/hashbrown — RepoGEO report