RRepoGEO

REPOGEO REPORT · LITE

facebookresearch/XLM

Default branch main · commit cd281d32 · scanned 5/20/2026, 3:27:48 AM

GitHub: 2,931 stars · 499 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
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 facebookresearch/XLM, 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
    Refine README's opening sentence for clearer positioning

    Why:

    CURRENT
    PyTorch original implementation of Cross-lingual Language Model Pretraining.
    COPY-PASTE FIX
    This repository provides the original PyTorch implementation of XLM, a research framework for Cross-lingual Language Model Pretraining, notably featuring the Translation Language Model (TLM) objective for explicit leveraging of parallel data.
  • mediumlicense#2
    Add a clear license statement to the README

    Why:

    COPY-PASTE FIX
    ## License
This project is licensed under the terms found in the [LICENSE](LICENSE) file.

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 facebookresearch/XLM
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
huggingface/transformers
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. huggingface/transformers · recommended 1×
  2. facebookresearch/fairseq · recommended 1×
  3. explosion/spaCy · recommended 1×
  4. stanfordnlp/stanza · recommended 1×
  5. OpenNMT/OpenNMT-py · recommended 1×
  • CATEGORY QUERY
    Seeking a robust framework for building multilingual NLP models and cross-lingual understanding.
    you: not recommended
    AI recommended (in order):
    1. Hugging Face Transformers (huggingface/transformers)
    2. fairseq (facebookresearch/fairseq)
    3. spaCy (explosion/spaCy)
    4. Stanza (stanfordnlp/stanza)
    5. OpenNMT (OpenNMT/OpenNMT-py)

    AI recommended 5 alternatives but never named facebookresearch/XLM. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools enable efficient pretraining of large language models for various NLP tasks?
    you: not recommended
    AI recommended (in order):
    1. Hugging Face Transformers
    2. PyTorch Lightning
    3. DeepSpeed
    4. Megatron-LM
    5. JAX/Flax
    6. TensorFlow
    7. Optimum

    AI recommended 7 alternatives but never named facebookresearch/XLM. 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 facebookresearch/XLM?
    pass
    AI named facebookresearch/XLM explicitly

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

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

Subscribe to Pro for deep diagnoses

facebookresearch/XLM — 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