RRepoGEO

REPOGEO REPORT · LITE

jalammar/ecco

Default branch main · commit 2a38a136 · scanned 5/27/2026, 9:36:57 PM

GitHub: 2,101 stars · 177 forks

AI VISIBILITY SCORE
82 /100
Healthy
Category recall
2 / 2
Avg rank #4.5 when recommended
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 jalammar/ecco, 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 README opening to emphasize unique value proposition

    Why:

    CURRENT
    Ecco is a python library for exploring and explaining Natural Language Processing models using interactive visualizations.
    COPY-PASTE FIX
    Ecco is a Python library for *interactive visualization and explanation* of Transformer-based language models (like GPT2, BERT, T5, T0) *directly within Jupyter notebooks*. It focuses solely on *understanding pre-trained models*, not training or fine-tuning.
  • mediumtopics#2
    Add specific topics for LLM interpretability and XAI

    Why:

    CURRENT
    explorables, language-models, natural-language-processing, nlp, pytorch, visualization
    COPY-PASTE FIX
    explorables, language-models, natural-language-processing, nlp, pytorch, visualization, llm-interpretability, explainable-ai, transformer-interpretability, xai
  • mediumcomparison#3
    Create a 'Comparison with Alternatives' section in README or documentation

    Why:

    COPY-PASTE FIX
    Add a new section, e.g., '## Comparison with Alternatives' or '## Why Ecco?', that briefly outlines how Ecco's interactive, visualization-centric approach for Transformer-based LLMs differs from other interpretability libraries like Captum, Transformers Interpret, LIME, or SHAP, especially regarding its focus on *exploring and understanding pre-trained models* in *Jupyter notebooks*.

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
2 / 2
100% of queries surface jalammar/ecco
Avg rank
#4.5
Lower is better. #1 = top recommendation.
Share of voice
15%
Of all named tools, what % are you?
Top rival
Transformers Interpret
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Transformers Interpret · recommended 2×
  2. Captum · recommended 2×
  3. LlamaIndex · recommended 1×
  4. TensorBoard · recommended 1×
  5. exBERT · recommended 1×
  • CATEGORY QUERY
    How can I visualize internal workings of large language models in Jupyter notebooks?
    you: #4
    AI recommended (in order):
    1. LlamaIndex
    2. Transformers Interpret
    3. Captum
    4. Ecco ← you
    5. TensorBoard
    6. exBERT
    Show full AI answer
  • CATEGORY QUERY
    Python library to explain and analyze Transformer-based language model behavior.
    you: #5
    AI recommended (in order):
    1. Captum
    2. Transformers Interpret
    3. LIME
    4. SHAP
    5. Ecco ← you
    6. Interpret-Text
    7. AllenNLP Interpret
    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 jalammar/ecco?
    pass
    AI named jalammar/ecco explicitly

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

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

Subscribe to Pro for deep diagnoses

jalammar/ecco — 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