RRepoGEO

REPOGEO REPORT · LITE

Junyi-99/ChatGPT-API-Scanner

Default branch main · commit 77685822 · scanned 6/9/2026, 3:48:13 PM

GitHub: 996 stars · 194 forks

AI VISIBILITY SCORE
28 /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
2 / 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 Junyi-99/ChatGPT-API-Scanner, 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 clarify its security research purpose

    Why:

    CURRENT
    This tool scans GitHub for available OpenAI API Keys.
    COPY-PASTE FIX
    This security research tool scans public GitHub repositories to identify accidentally exposed OpenAI API Keys.
  • hightopics#2
    Add specific topics related to secret scanning and leak detection

    Why:

    CURRENT
    chatgpt, chatgpt-api, freegpt, gpt, gpt-3, gpt4, selenium
    COPY-PASTE FIX
    chatgpt, chatgpt-api, freegpt, gpt, gpt-3, gpt4, selenium, secret-scanning, api-key-leak, security-research, leak-detection, github-scanner
  • mediumhomepage#3
    Add the repository URL as the homepage link

    Why:

    COPY-PASTE FIX
    https://github.com/Junyi-99/ChatGPT-API-Scanner

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 Junyi-99/ChatGPT-API-Scanner
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
GitHub Advanced Security
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. GitHub Advanced Security · recommended 1×
  2. Have I Been Pwned · recommended 1×
  3. GitGuardian/ggshield · recommended 1×
  4. trufflesecurity/trufflehog · recommended 1×
  5. gitleaks/gitleaks · recommended 1×
  • CATEGORY QUERY
    How can I check if my OpenAI API keys have been accidentally exposed on public platforms?
    you: not recommended
    AI recommended (in order):
    1. GitHub Advanced Security
    2. Have I Been Pwned
    3. GitGuardian ggshield (GitGuardian/ggshield)
    4. TruffleHog (trufflesecurity/trufflehog)
    5. Gitleaks (gitleaks/gitleaks)
    6. AWS Secrets Manager
    7. Azure Key Vault
    8. Google Secret Manager
    9. dotenv (motdotla/dotenv)

    AI recommended 9 alternatives but never named Junyi-99/ChatGPT-API-Scanner. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools help monitor public code repositories for accidental exposure of sensitive API credentials?
    you: not recommended
    AI recommended (in order):
    1. GitGuardian Internal Monitoring
    2. GitHub Advanced Security (Secret Scanning)
    3. TruffleHog
    4. Gitleaks
    5. SpectralOps
    6. Snyk Code (Secret Detection)
    7. Detectify

    AI recommended 7 alternatives but never named Junyi-99/ChatGPT-API-Scanner. 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 Junyi-99/ChatGPT-API-Scanner?
    pass
    AI did not name Junyi-99/ChatGPT-API-Scanner — 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 Junyi-99/ChatGPT-API-Scanner in production, what risks or prerequisites should they evaluate first?
    pass
    AI named Junyi-99/ChatGPT-API-Scanner 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 Junyi-99/ChatGPT-API-Scanner solve, and who is the primary audience?
    pass
    AI named Junyi-99/ChatGPT-API-Scanner 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 Junyi-99/ChatGPT-API-Scanner. 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/Junyi-99/ChatGPT-API-Scanner.svg)](https://repogeo.com/en/r/Junyi-99/ChatGPT-API-Scanner)
HTML
<a href="https://repogeo.com/en/r/Junyi-99/ChatGPT-API-Scanner"><img src="https://repogeo.com/badge/Junyi-99/ChatGPT-API-Scanner.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

Junyi-99/ChatGPT-API-Scanner — 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