RRepoGEO

REPOGEO REPORT · LITE

kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference

Default branch main · commit 187c1ee3 · scanned 6/3/2026, 6:22:41 PM

GitHub: 974 stars · 207 forks

AI VISIBILITY SCORE
27 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
1 / 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 kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference, 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's opening to clarify project type and core technology

    Why:

    CURRENT
    ### Clearly explained guide for running quantized open-source LLM applications on CPUs using LLama 2, C Transformers, GGML, and LangChain
    COPY-PASTE FIX
    ### A practical, step-by-step guide and example project demonstrating how to run quantized open-source LLMs like Llama 2 on CPU for document Q&A, specifically leveraging C Transformers, GGML, and LangChain for efficient local inference.
  • highreadme#2
    Add a 'Key Technologies' or 'Approach' section to highlight specific CPU optimization

    Why:

    COPY-PASTE FIX
    ## Key Technologies & Approach
    This project specifically focuses on demonstrating efficient CPU inference by leveraging optimized frameworks such as C Transformers and GGML. This approach enables robust local LLM deployment for document Q&A, significantly reducing reliance on costly GPU instances while maintaining practical performance.
  • mediumtopics#3
    Add 'tutorial' and 'example-project' to repository topics

    Why:

    CURRENT
    c-transformers, chatgpt, cpu, cpu-inference, deep-learning, document-qa, faiss, langchain, language-models, large-language-models, llama, llama-2, llm, machine-learning, natural-language-processing, nlp, open-source-llm, python, sentence-transformers, transformers
    COPY-PASTE FIX
    c-transformers, chatgpt, cpu, cpu-inference, deep-learning, document-qa, example-project, faiss, langchain, language-models, large-language-models, llama, llama-2, llm, machine-learning, natural-language-processing, nlp, open-source-llm, python, sentence-transformers, transformers, tutorial

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 kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LM Studio
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. LM Studio · recommended 2×
  2. ollama/ollama · recommended 1×
  3. nomic-ai/gpt4all · recommended 1×
  4. huggingface/transformers · recommended 1×
  5. OpenNMT/CTranslate2 · recommended 1×
  • CATEGORY QUERY
    How to run open-source large language models locally on CPU for document question answering?
    you: not recommended
    AI recommended (in order):
    1. Ollama (ollama/ollama)
    2. LM Studio
    3. GPT4All (nomic-ai/gpt4all)
    4. Hugging Face Transformers (huggingface/transformers)
    5. ctranslate2 (OpenNMT/CTranslate2)
    6. optimum (huggingface/optimum)
    7. ONNX Runtime (microsoft/onnxruntime)
    8. llama.cpp (ggerganov/llama.cpp)
    9. llama-cpp-python (abetlen/llama-cpp-python)
    10. LangChain (langchain-ai/langchain)
    11. LlamaIndex (run-llama/llama_index)
    12. sentence-transformers (UKPLab/sentence-transformers)
    13. FAISS (facebookresearch/faiss)
    14. Chroma (chroma-core/chroma)
    15. LanceDB (lancedb/lancedb)

    AI recommended 15 alternatives but never named kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a solution to deploy open-source LLMs on local hardware for private document processing.
    you: not recommended
    AI recommended (in order):
    1. Ollama
    2. LM Studio
    3. Jan
    4. text-generation-webui (oobabooga/text-generation-webui)
    5. LocalAI
    6. llama.cpp
    7. Transformers

    AI recommended 7 alternatives but never named kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference. This is the gap to close.

    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 kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference?
    pass
    AI did not name kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference — likely talking about a different project

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

  • If a team adopts kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference in production, what risks or prerequisites should they evaluate first?
    pass
    AI named kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference 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 kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference solve, and who is the primary audience?
    pass
    AI did not name kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference — likely talking about a different project

    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 kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference. 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/kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference.svg)](https://repogeo.com/en/r/kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference)
HTML
<a href="https://repogeo.com/en/r/kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference"><img src="https://repogeo.com/badge/kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

kennethleungty/Llama-2-Open-Source-LLM-CPU-Inference — 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