RRepoGEO

REPOGEO REPORT · LITE

zeux/calm

Default branch main · commit cab0b7b4 · scanned 6/12/2026, 12:12:52 PM

GitHub: 642 stars · 31 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 zeux/calm, 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 H1 to clarify calm's identity as an LLM inference engine

    Why:

    CURRENT
    # 😌 calm
    
    This is an implementation of language model inference, aiming to get maximum single-GPU single-batch hardware utilization for LLM architectures with a minimal implementation and no dependencies[^1].
    COPY-PASTE FIX
    # 😌 calm: A Minimal LLM Inference Engine for CUDA/Metal
    
    This project, `calm`, is an implementation of language model inference, aiming to get maximum single-GPU single-batch hardware utilization for LLM architectures with a minimal implementation and no dependencies[^1]. It focuses on CUDA/Metal acceleration for LLMs.
  • mediumabout#2
    Enhance the repository description with more specific keywords

    Why:

    CURRENT
    CUDA/Metal accelerated language model inference
    COPY-PASTE FIX
    Minimal, dependency-free CUDA/Metal accelerated language model (LLM) inference engine for single-GPU utilization.
  • mediumtopics#3
    Add more specific LLM inference topics

    Why:

    CURRENT
    cuda, llm-inference, ml
    COPY-PASTE FIX
    cuda, llm-inference, ml, metal, gpu-inference, language-models, llama-cpp-alternative, transformer-inference

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 zeux/calm
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
vLLM
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. vLLM · recommended 1×
  2. Hugging Face `transformers` · recommended 1×
  3. `bitsandbytes` · recommended 1×
  4. TensorRT-LLM · recommended 1×
  5. llama.cpp · recommended 1×
  • CATEGORY QUERY
    How to achieve maximum single-GPU utilization for LLM inference with minimal dependencies?
    you: not recommended
    AI recommended (in order):
    1. vLLM
    2. Hugging Face `transformers`
    3. `bitsandbytes`
    4. TensorRT-LLM
    5. llama.cpp
    6. DeepSpeed-MII

    AI recommended 6 alternatives but never named zeux/calm. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a fast, low-dependency solution for CUDA or Metal LLM inference.
    you: not recommended
    AI recommended (in order):
    1. llama.cpp (ggerganov/llama.cpp)
    2. MLX (ml-explore/mlx)
    3. TensorRT-LLM (NVIDIA/TensorRT-LLM)
    4. ONNX Runtime (microsoft/onnxruntime)
    5. GGML (ggerganov/ggml)

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

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

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

Subscribe to Pro for deep diagnoses

zeux/calm — 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