RRepoGEO

REPOGEO REPORT · LITE

MorDavid/BruteForceAI

Default branch main · commit 0f64b278 · scanned 5/16/2026, 10:52:43 AM

GitHub: 1,426 stars · 264 forks

AI VISIBILITY SCORE
33 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 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 MorDavid/BruteForceAI, 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 main description to explicitly state its purpose as a penetration testing tool

    Why:

    CURRENT
    **Advanced LLM-powered brute-force tool combining AI intelligence with automated login attacks**
    COPY-PASTE FIX
    **Advanced LLM-powered brute-force penetration testing tool combining AI intelligence with automated login attacks**
  • hightopics#2
    Add more specific cybersecurity and penetration testing topics

    Why:

    CURRENT
    ai, bruteforce, bugbounty, llm, loginpages
    COPY-PASTE FIX
    ai, bruteforce, bugbounty, llm, loginpages, penetration-testing, cybersecurity, red-teaming, ethical-hacking
  • mediumreadme#3
    Clarify the existing license in the README's License section

    Why:

    COPY-PASTE FIX
    Add a sentence to the 'License' section in your README, such as: 'Please refer to the `LICENSE` file for specific terms and conditions regarding 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 MorDavid/BruteForceAI
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Nessus
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Nessus · recommended 1×
  2. OpenVAS · recommended 1×
  3. Acunetix · recommended 1×
  4. Cloudflare WAF · recommended 1×
  5. ModSecurity · recommended 1×
  • CATEGORY QUERY
    How can I use AI to intelligently identify login forms and automate brute-force attacks?
    you: not recommended
    AI recommended (in order):
    1. Nessus
    2. OpenVAS
    3. Acunetix
    4. Cloudflare WAF
    5. ModSecurity
    6. AWS WAF
    7. CompTIA Security+
    8. Certified Ethical Hacker (CEH)
    9. Offensive Security Certified Professional (OSCP)
    10. HackerOne
    11. Bugcrowd

    AI recommended 11 alternatives but never named MorDavid/BruteForceAI. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are some advanced tools for automated login brute-force attacks with human-like evasion?
    you: not recommended
    AI recommended (in order):
    1. Burp Suite Professional
    2. Turbo Intruder
    3. Logger++
    4. Hydra
    5. ProxyChains
    6. OWASP ZAP
    7. GoBuster
    8. ffuf
    9. Requests
    10. Mechanize
    11. Scrapy
    12. Selenium
    13. 2Captcha
    14. Anti-Captcha
    15. HTTParty
    16. net/http
    17. colly

    AI recommended 17 alternatives but never named MorDavid/BruteForceAI. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

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

Subscribe to Pro for deep diagnoses

MorDavid/BruteForceAI — 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