RRepoGEO

REPOGEO REPORT · LITE

HazyResearch/legalbench

Default branch main · commit b46bf4ff · scanned 6/1/2026, 10:32:47 AM

GitHub: 587 stars · 91 forks

AI VISIBILITY SCORE
76 /100
Needs work
Category recall
2 / 2
Avg rank #3.0 when recommended
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 HazyResearch/legalbench, 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
  • hightopics#1
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    llm-benchmark, legal-nlp, natural-language-processing, legal-ai, machine-learning, evaluation, datasets, legal-reasoning
  • highlicense#2
    Create a LICENSE file in the repository root

    Why:

    CURRENT
    (no LICENSE file detected — the repo has no recognizable license)
    COPY-PASTE FIX
    Create a LICENSE file in the repository root, choosing an appropriate open-source license (e.g., MIT, Apache-2.0) and adding the full license text.
  • mediumabout#3
    Add the project homepage URL to the repository's 'About' section

    Why:

    COPY-PASTE FIX
    Add the official project website URL to the 'Website' field in the repository's 'About' section.

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 HazyResearch/legalbench
Avg rank
#3.0
Lower is better. #1 = top recommendation.
Share of voice
10%
Of all named tools, what % are you?
Top rival
COLIEE
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. COLIEE · recommended 2×
  2. LeXFiles · recommended 2×
  3. CaseHOLD · recommended 2×
  4. HELM · recommended 1×
  5. LexisNexis Academic · recommended 1×
  • CATEGORY QUERY
    How to benchmark large language models on legal reasoning tasks?
    you: #1
    AI recommended (in order):
    1. LegalBench ← you
    2. HELM
    3. LexisNexis Academic
    4. Westlaw
    5. Practical Law
    6. Prodigy
    7. Doccano
    8. COLIEE
    9. LeXFiles
    10. CaseHOLD
    11. Amazon Mechanical Turk
    12. Upwork
    13. TextAttack
    Show full AI answer
  • CATEGORY QUERY
    Where can I find datasets to evaluate AI performance on legal questions?
    you: #5
    AI recommended (in order):
    1. LexGLUE
    2. COLIEE
    3. CaseHOLD
    4. LeXFiles
    5. LegalBench ← you
    6. Stanford Question Answering Dataset (SQuAD)
    7. Kaggle
    8. Hugging Face Datasets
    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 HazyResearch/legalbench?
    pass
    AI named HazyResearch/legalbench 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/legalbench in production, what risks or prerequisites should they evaluate first?
    pass
    AI named HazyResearch/legalbench 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/legalbench solve, and who is the primary audience?
    pass
    AI named HazyResearch/legalbench 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/legalbench. 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/legalbench.svg)](https://repogeo.com/en/r/HazyResearch/legalbench)
HTML
<a href="https://repogeo.com/en/r/HazyResearch/legalbench"><img src="https://repogeo.com/badge/HazyResearch/legalbench.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

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