RRepoGEO

REPOGEO REPORT · LITE

Austin1serb/Anthropic-Leaked-Source-Code

Default branch main · commit 3fa80a44 · scanned 6/29/2026, 11:03:33 AM

GitHub: 500 stars · 739 forks

AI VISIBILITY SCORE
22 /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
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 Austin1serb/Anthropic-Leaked-Source-Code, 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 introduction to clarify archive status

    Why:

    CURRENT
    This repository contains an unmodified archive of the leaked source code for Claude Code, Anthropic's AI-powered coding agent.
    COPY-PASTE FIX
    This repository contains an unmodified archive of the leaked source code for Claude Code, Anthropic's AI-powered coding agent. It is provided strictly for research, education, and technical analysis of a real-world AI system's internal structure, and is not intended for direct use, implementation, or as a guide for best practices.
  • highlicense#2
    Add a LICENSE file

    Why:

    COPY-PASTE FIX
    Create a `LICENSE` file in the repository root to explicitly define the legal terms for accessing and studying the leaked source code.
  • mediumreadme#3
    Add a dedicated Disclaimer section to README

    Why:

    COPY-PASTE FIX
    Add a new section to the README, perhaps titled 'Important Disclaimer' or 'Usage Notice', explicitly stating that this repository is an archive of leaked material, not an official release, and should not be used for production, commercial purposes, or as a basis for developing new tools without independent verification and legal counsel.

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 Austin1serb/Anthropic-Leaked-Source-Code
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LangChain
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. LangChain · recommended 2×
  2. LlamaIndex · recommended 2×
  3. ESLint · recommended 2×
  4. VS Code · recommended 1×
  5. JetBrains IDEs · recommended 1×
  • CATEGORY QUERY
    How are modern AI coding assistants architected, including agent orchestration and tool integration?
    you: not recommended
    AI recommended (in order):
    1. VS Code
    2. JetBrains IDEs
    3. Neovim
    4. GPT-4
    5. Claude 3
    6. Gemini 1.5 Pro
    7. Llama 3
    8. LangChain
    9. LlamaIndex
    10. AutoGen
    11. CrewAI
    12. Marvin
    13. Git
    14. ESLint
    15. Prettier
    16. Black
    17. Ruff
    18. pdb
    19. GDB
    20. VS Code Debugger API
    21. Jest
    22. Pytest
    23. JUnit
    24. Stack Overflow
    25. MDN Web Docs
    26. npm
    27. pip
    28. Maven
    29. Gradle
    30. Chroma
    31. Pinecone
    32. Weaviate
    33. FAISS

    AI recommended 33 alternatives but never named Austin1serb/Anthropic-Leaked-Source-Code. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are best practices for prompt construction and sandboxing in AI-powered developer tools?
    you: not recommended
    AI recommended (in order):
    1. OpenAI Playground
    2. Anthropic Console
    3. LangChain
    4. LlamaIndex
    5. Guardrails AI
    6. Weights & Biases Prompts
    7. MLflow AI Gateway
    8. Docker
    9. cgroups
    10. iptables
    11. AWS Security Groups
    12. Azure Network Security Groups
    13. Kubernetes
    14. AWS Fargate
    15. Google Cloud Run
    16. ESLint
    17. Pylint
    18. SonarQube
    19. Semgrep
    20. GitHub Pull Requests

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

Subscribe to Pro for deep diagnoses

Austin1serb/Anthropic-Leaked-Source-Code — 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