RRepoGEO

REPOGEO REPORT · LITE

lillian039/ELF

Default branch main · commit a843d30e · scanned 5/21/2026, 6:03:51 AM

GitHub: 670 stars · 41 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
30 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 0 warn · 1 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 lillian039/ELF, 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
  • highabout#1
    Add a concise repository description

    Why:

    COPY-PASTE FIX
    ELF (Embedded Language Flows) is a JAX implementation of continuous diffusion language models, leveraging flow matching and continuous embedding spaces for text generation.
  • mediumhomepage#2
    Add a homepage URL to the repository

    Why:

    COPY-PASTE FIX
    https://huggingface.co/embedded-language-flows

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 lillian039/ELF
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GLIDE
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. GLIDE · recommended 2×
  2. Diffusers · recommended 1×
  3. PyTorch · recommended 1×
  4. PyTorch Lightning · recommended 1×
  5. JAX · recommended 1×
  • CATEGORY QUERY
    How to build language models using continuous diffusion techniques for better embedding space handling?
    you: not recommended
    AI recommended (in order):
    1. Diffusers
    2. PyTorch
    3. PyTorch Lightning
    4. JAX
    5. Flax
    6. Haiku
    7. TensorFlow
    8. Keras
    9. OpenAI's Diffusion Model Implementations
    10. GLIDE
    11. DALL-E 2

    AI recommended 11 alternatives but never named lillian039/ELF. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Are there language model architectures that leverage image diffusion techniques like classifier-free guidance?
    you: not recommended
    AI recommended (in order):
    1. Diffusion-LM
    2. DiffuSeq
    3. Nuwa-Infinity
    4. GLIDE

    AI recommended 4 alternatives but never named lillian039/ELF. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    fail

    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 lillian039/ELF?
    pass
    AI named lillian039/ELF explicitly

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

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

Subscribe to Pro for deep diagnoses

lillian039/ELF — 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