RRepoGEO

REPOGEO REPORT · LITE

wyeeeee/hajimi

Default branch main · commit 3712ba49 · scanned 6/19/2026, 12:47:41 AM

GitHub: 1,740 stars · 5,395 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 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

2 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Add a concise English summary to the README's introduction

    Why:

    COPY-PASTE FIX
    HAJIMI is a FastAPI-based proxy for Google's Gemini API, designed to provide a simple, secure, and configurable way to access Gemini models. It supports OpenAI API format for tool integration and is ideal for deployment on platforms like Hugging Face Spaces. This proxy also features API key rotation, password protection, and a fake streaming mode to enhance reliability.
  • mediumreadme#2
    Clarify the existing license in the README

    Why:

    COPY-PASTE FIX
    ## 📄 License
This project is released under [describe your license(s) here, e.g., 'a custom license based on X and Y' or 'multiple licenses as detailed in the LICENSE file']. Please refer to the `LICENSE` file for full details.

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
OpenRouter
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. OpenRouter · recommended 2×
  2. LiteLLM · recommended 1×
  3. LocalAI · recommended 1×
  4. vLLM · recommended 1×
  5. FastChat · recommended 1×
  • CATEGORY QUERY
    How can I use a different large language model with tools expecting the OpenAI API format?
    you: not recommended
    AI recommended (in order):
    1. LiteLLM
    2. OpenRouter
    3. LocalAI
    4. vLLM
    5. FastChat
    6. Ollama
    7. LangChain

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

    Show full AI answer
  • CATEGORY QUERY
    Looking for a service to manage multiple AI model API keys and provide a unified endpoint.
    you: not recommended
    AI recommended (in order):
    1. OpenRouter
    2. LiteLLM (BerriAI/litellm)
    3. Portkey.ai
    4. Helicone
    5. Azure AI Studio
    6. AWS Bedrock

    AI recommended 6 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