RRepoGEO

REPOGEO REPORT · LITE

evilsocket/audit

Default branch main · commit d6ee7303 · scanned 6/11/2026, 3:43:09 PM

GitHub: 608 stars · 89 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 evilsocket/audit, 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 specific topics to clarify the project's domain

    Why:

    COPY-PASTE FIX
    ["ai-agent", "vulnerability-discovery", "code-security", "llm", "claude", "security-auditing", "generative-ai"]
  • highreadme#2
    Reposition the README's opening to explicitly state 'code vulnerability' and AI focus

    Why:

    CURRENT
    # audit

An 8-stage vulnerability-discovery agent, driven by your **Claude Pro / Max subscription** through the official Claude Code Agent SDK.
    COPY-PASTE FIX
    # audit: AI-driven Code Vulnerability Discovery Agent

This project, `audit`, is an 8-stage **AI-driven code vulnerability discovery agent**, driven by your **Claude Pro / Max subscription** through the official Claude Code Agent SDK. It is designed for finding security flaws in *codebases*, not for system log analysis.
  • mediumhomepage#3
    Add a homepage URL to provide an external reference

    Why:

    COPY-PASTE FIX
    (Add a relevant URL, e.g., a project website, blog post, or a dedicated GitHub Pages site)

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 evilsocket/audit
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. CodeQL · recommended 1×
  3. Dependabot · recommended 1×
  4. Snyk · recommended 1×
  5. Snyk Code · recommended 1×
  • CATEGORY QUERY
    How to automate security vulnerability scanning in codebases using AI agents?
    you: not recommended
    AI recommended (in order):
    1. GitHub Advanced Security
    2. CodeQL
    3. Dependabot
    4. Snyk
    5. Snyk Code
    6. Snyk Open Source
    7. Snyk Container
    8. Snyk Infrastructure as Code (IaC)
    9. Checkmarx One
    10. Checkmarx SAST
    11. Sonatype Nexus Lifecycle
    12. Veracode Static Analysis
    13. Bandit
    14. Semgrep
    15. Semgrep AppSec Platform
    16. OpenAI GPT-4
    17. Google Gemini
    18. Anthropic Claude

    AI recommended 18 alternatives but never named evilsocket/audit. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Tool for finding code vulnerabilities with multiple AI agents and reachability analysis?
    you: not recommended
    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 evilsocket/audit?
    pass
    AI did not name evilsocket/audit — 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 evilsocket/audit in production, what risks or prerequisites should they evaluate first?
    pass
    AI named evilsocket/audit 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 evilsocket/audit solve, and who is the primary audience?
    pass
    AI named evilsocket/audit 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 evilsocket/audit. 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/evilsocket/audit.svg)](https://repogeo.com/en/r/evilsocket/audit)
HTML
<a href="https://repogeo.com/en/r/evilsocket/audit"><img src="https://repogeo.com/badge/evilsocket/audit.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

evilsocket/audit — 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