RRepoGEO

REPOGEO REPORT · LITE

HazyResearch/safari

Default branch main · commit 02220c69 · scanned 5/30/2026, 12:48:06 PM

GitHub: 913 stars · 70 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 HazyResearch/safari, 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
  • highreadme#1
    Clarify the README's opening paragraph to explicitly state the repo's role as a transformer alternative for long sequences

    Why:

    CURRENT
    This repository provides implementations and experiments for the following papers, as well as simplified presentations of earlier work such as S4.
    COPY-PASTE FIX
    This repository provides efficient implementations and experiments for novel convolutional and state-space model (SSM) architectures, offering scalable alternatives to Transformers for processing very long sequences in language modeling and other tasks. It includes implementations for papers such as H3, Hyena, and Long Convs, as well as simplified presentations of earlier work such as S4.
  • mediumhomepage#2
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    [Insert relevant project or lab homepage URL here, e.g., https://hazyresearch.stanford.edu/projects/safari]

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 HazyResearch/safari
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Performer
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Performer · recommended 2×
  2. Linformer · recommended 2×
  3. Transformer-XL · recommended 1×
  4. XLNet · recommended 1×
  5. Longformer · recommended 1×
  • CATEGORY QUERY
    How to efficiently process very long sequences for language modeling tasks?
    you: not recommended
    AI recommended (in order):
    1. Transformer-XL
    2. XLNet
    3. Longformer
    4. BigBird
    5. Reformer
    6. Performer
    7. Linformer
    8. Hugging Face's `transformers` library

    AI recommended 8 alternatives but never named HazyResearch/safari. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking alternatives to transformer architectures for large-scale, efficient sequence processing.
    you: not recommended
    AI recommended (in order):
    1. LSTMs
    2. GRUs
    3. Mamba
    4. TCNs
    5. WaveNet
    6. ByteNet
    7. Performer
    8. Linformer
    9. Nyströmformer
    10. S4
    11. S5
    12. SRU

    AI recommended 12 alternatives but never named HazyResearch/safari. 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 HazyResearch/safari?
    pass
    AI named HazyResearch/safari explicitly

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

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

Subscribe to Pro for deep diagnoses

HazyResearch/safari — 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