RRepoGEO

REPOGEO REPORT · LITE

jmaczan/tiny-vllm

Default branch main · commit 6aa2de81 · scanned 6/12/2026, 8:03:21 AM

GitHub: 785 stars · 49 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 jmaczan/tiny-vllm, 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 the README's opening sentence to emphasize the educational aspect

    Why:

    CURRENT
    You're going to build a high performance LLM inference engine with C++ and CUDA - tiny-vllm, a younger and smaller sibling of vLLM
    COPY-PASTE FIX
    Learn to build your own high performance LLM inference engine with C++ and CUDA from scratch, following this course on tiny-vllm, a younger and smaller sibling of vLLM.
  • mediumtopics#2
    Add more explicit educational topics

    Why:

    CURRENT
    ai, attention, batching, course, cpp, cuda, hpc, inference, llm, llm-inference, pagedattention, tiny-vllm, vllm
    COPY-PASTE FIX
    ai, attention, batching, course, cpp, cuda, education, hpc, inference, learning, llm, llm-inference, pagedattention, tiny-vllm, tutorial, vllm
  • lowhomepage#3
    Add a homepage URL to the repository's About section

    Why:

    COPY-PASTE FIX
    https://github.com/jmaczan/tiny-vllm

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 jmaczan/tiny-vllm
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
NVIDIA/TensorRT
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. NVIDIA/TensorRT · recommended 1×
  2. NVIDIA/FasterTransformer · recommended 1×
  3. triton-inference-server/server · recommended 1×
  4. openvinotoolkit/openvino · recommended 1×
  5. ggerganov/llama.cpp · recommended 1×
  • CATEGORY QUERY
    How can I build a high-performance LLM inference engine using C++ and CUDA?
    you: not recommended
    AI recommended (in order):
    1. NVIDIA TensorRT (NVIDIA/TensorRT)
    2. NVIDIA FasterTransformer (NVIDIA/FasterTransformer)
    3. NVIDIA Triton Inference Server (triton-inference-server/server)
    4. OpenVINO (openvinotoolkit/openvino)
    5. llama.cpp (ggerganov/llama.cpp)
    6. PyTorch (pytorch/pytorch)
    7. TensorFlow (tensorflow/tensorflow)
    8. ONNX (onnx/onnx)

    AI recommended 8 alternatives but never named jmaczan/tiny-vllm. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a guide to implement advanced LLM inference optimizations like PagedAttention and continuous batching.
    you: not recommended
    AI recommended (in order):
    1. vLLM
    2. TGI (Text Generation Inference)
    3. DeepSpeed-MII (Microsoft Inference Interface)
    4. TensorRT-LLM
    5. OpenVINO

    AI recommended 5 alternatives but never named jmaczan/tiny-vllm. 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 jmaczan/tiny-vllm?
    pass
    AI named jmaczan/tiny-vllm explicitly

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

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

Subscribe to Pro for deep diagnoses

jmaczan/tiny-vllm — 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