RRepoGEO

REPOGEO REPORT · LITE

wyeeeee/hajimi

Default branch main · commit 3712ba49 · scanned 5/9/2026, 5:46:43 AM

GitHub: 1,743 stars · 5,425 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 wyeeeee/hajimi, 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 for LLM API proxy

    Why:

    COPY-PASTE FIX
    llm-proxy, gemini-api, openai-api-compatible, fastapi, python, ai-gateway, model-management, self-hosted
  • highreadme#2
    Add a clear statement about the project's license(s) to the README

    Why:

    COPY-PASTE FIX
    本项目采用 [具体许可证名称，例如：MIT License 或 Apache-2.0 License] 授权。详情请参阅仓库中的 `LICENSE` 文件。
  • mediumhomepage#3
    Add a homepage URL to the repository settings

    Why:

    COPY-PASTE FIX
    [URL to a live demo, documentation site, or the main repository page, e.g., https://github.com/wyeeeee/hajimi]

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 wyeeeee/hajimi
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LiteLLM
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. LiteLLM · recommended 2×
  2. Caddy · recommended 2×
  3. OpenRouter · recommended 1×
  4. LocalAI · recommended 1×
  5. vLLM · recommended 1×
  • CATEGORY QUERY
    How can I integrate a new large language model into tools expecting OpenAI API format?
    you: not recommended
    AI recommended (in order):
    1. LiteLLM
    2. OpenRouter
    3. LocalAI
    4. vLLM
    5. FastChat
    6. Ollama
    7. NGINX
    8. Caddy
    9. Python
    10. Flask
    11. FastAPI

    AI recommended 11 alternatives but never named wyeeeee/hajimi. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a self-hosted proxy to manage multiple AI model keys and provide a unified interface.
    you: not recommended
    AI recommended (in order):
    1. OpenAI Proxy
    2. LiteLLM
    3. Portkey.ai
    4. Helicone.ai
    5. Nginx
    6. OpenResty
    7. Caddy

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

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

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

Subscribe to Pro for deep diagnoses

wyeeeee/hajimi — 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