RRepoGEO

REPOGEO REPORT · LITE

heymrun/heym

Default branch main · commit ddc89416 · scanned 6/10/2026, 5:51:54 AM

GitHub: 576 stars · 63 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

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 heymrun/heym, 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

2 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • mediumcomparison#1
    Add a 'Why Heym?' or 'Heym vs. Alternatives' section to the README.

    Why:

    COPY-PASTE FIX
    Add a new section to the README (e.g., after 'What Is Heym?') titled 'Why Heym?' or 'Heym vs. Alternatives' that highlights its unique AI-native approach compared to tools like Langflow, FlowiseAI, N8n, Prefect, or Apache Airflow.
  • lowlicense#2
    Clarify the project's license in the README.

    Why:

    COPY-PASTE FIX
    Add a clear statement in the README (e.g., in a 'License' or 'Contributing' section) explaining the terms of the LICENSE file and COMMONS-CLAUSE.md that apply to the project.

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 heymrun/heym
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Langflow
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Langflow · recommended 1×
  2. FlowiseAI · recommended 1×
  3. N8n · recommended 1×
  4. Prefect · recommended 1×
  5. Apache Airflow · recommended 1×
  • CATEGORY QUERY
    Looking for a self-hosted platform to visually build and orchestrate AI agent workflows.
    you: not recommended
    AI recommended (in order):
    1. Langflow
    2. FlowiseAI
    3. N8n
    4. Prefect
    5. Apache Airflow
    6. Temporal

    AI recommended 6 alternatives but never named heymrun/heym. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are open-source tools for AI workflow automation with RAG and human-in-the-loop?
    you: not recommended
    AI recommended (in order):
    1. LangChain (langchain-ai/langchain)
    2. LlamaIndex (run-llama/llama_index)
    3. Haystack (deepset-ai/haystack)
    4. Apache Airflow (apache/airflow)
    5. Prefect (PrefectHQ/prefect)
    6. MLflow (mlflow/mlflow)
    7. Cortex (cortexlabs/cortex)

    AI recommended 7 alternatives but never named heymrun/heym. 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 heymrun/heym?
    pass
    AI did not name heymrun/heym — 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 heymrun/heym in production, what risks or prerequisites should they evaluate first?
    pass
    AI named heymrun/heym 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 heymrun/heym solve, and who is the primary audience?
    pass
    AI named heymrun/heym 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 heymrun/heym. 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/heymrun/heym.svg)](https://repogeo.com/en/r/heymrun/heym)
HTML
<a href="https://repogeo.com/en/r/heymrun/heym"><img src="https://repogeo.com/badge/heymrun/heym.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

heymrun/heym — 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