RRepoGEO

REPOGEO REPORT · LITE

zakirkun/deep-eye

Default branch main · commit 0245daba · scanned 6/27/2026, 3:26:39 AM

GitHub: 1,776 stars · 322 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)

3 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 zakirkun/deep-eye, 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

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

OVERALL DIRECTION
  • mediumreadme#1
    Clarify the existing license in the README

    Why:

    COPY-PASTE FIX
    Add a section like "## License" to your README, clearly stating the terms under which Deep Eye is distributed, referencing the existing LICENSE file, e.g., "Deep Eye is distributed under the terms specified in the [LICENSE](LICENSE) file. Please review the file for full details on usage and distribution."

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 zakirkun/deep-eye
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
OWASP ZAP
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. OWASP ZAP · recommended 1×
  2. Burp Suite Enterprise Edition · recommended 1×
  3. Nuclei · recommended 1×
  4. Arachni Scanner · recommended 1×
  5. Scrapy · recommended 1×
  • CATEGORY QUERY
    How to automate web vulnerability scanning with AI-generated intelligent payloads and reporting?
    you: not recommended
    AI recommended (in order):
    1. OWASP ZAP
    2. Burp Suite Enterprise Edition
    3. Nuclei
    4. Arachni Scanner
    5. Scrapy
    6. requests
    7. TensorFlow
    8. PyTorch
    9. Hugging Face Transformers
    10. Veracode DAST Essentials
    11. Checkmarx DAST
    12. GPT-4
    13. Llama

    AI recommended 13 alternatives but never named zakirkun/deep-eye. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools use multiple large language models for comprehensive security vulnerability assessments?
    you: not recommended
    AI recommended (in order):
    1. Gryphos AI
    2. CodeQL
    3. GitHub Copilot Enterprise
    4. Semgrep
    5. Semgrep Code
    6. OWASP LLM Security Project
    7. LangChain
    8. LlamaIndex
    9. OpenAI GPT-4
    10. Anthropic Claude
    11. Google Gemini
    12. Prowler

    AI recommended 12 alternatives but never named zakirkun/deep-eye. 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 zakirkun/deep-eye?
    pass
    AI named zakirkun/deep-eye explicitly

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

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

Subscribe to Pro for deep diagnoses

zakirkun/deep-eye — 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