RRepoGEO

REPOGEO REPORT · LITE

trustedsec/hate_crack

Default branch main · commit 905c097b · scanned 6/27/2026, 2:06:54 PM

GitHub: 1,839 stars · 283 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 trustedsec/hate_crack, 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

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

OVERALL DIRECTION
  • highreadme#1
    Add a clear license statement to the README

    Why:

    COPY-PASTE FIX
    Add a clear statement to the README, ideally near the top, specifying the license under which hate_crack is distributed. For example: 'hate_crack is released under the [Insert License Name Here, e.g., MIT License, Apache 2.0 License, or a custom license].'
  • mediumreadme#2
    Add a concise value proposition above the ASCII art in README

    Why:

    COPY-PASTE FIX
    Add the following sentence (or similar) at the very top of the README, before the ASCII art: 'hate_crack is an advanced, automated password cracking utility designed for penetration testers and security professionals, streamlining complex Hashcat workflows for security audits and red team operations.'

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 trustedsec/hate_crack
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
hashcat/hashcat
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. hashcat/hashcat · recommended 2×
  2. openwall/john · recommended 2×
  3. vanhauser-thc/thc-hydra · recommended 2×
  4. Cain & Abel · recommended 2×
  5. aircrack-ng/aircrack-ng · recommended 2×
  • CATEGORY QUERY
    What tools can help automate common password cracking techniques for security audits?
    you: not recommended
    AI recommended (in order):
    1. Hashcat (hashcat/hashcat)
    2. John the Ripper (openwall/john)
    3. Hydra (vanhauser-thc/thc-hydra)
    4. Medusa (jmkng/medusa)
    5. Cain & Abel
    6. Aircrack-ng (aircrack-ng/aircrack-ng)

    AI recommended 6 alternatives but never named trustedsec/hate_crack. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a robust utility to streamline dictionary attacks and brute-force operations against password hashes.
    you: not recommended
    AI recommended (in order):
    1. Hashcat (hashcat/hashcat)
    2. John the Ripper (openwall/john)
    3. Hydra (vanhauser-thc/thc-hydra)
    4. Aircrack-ng (aircrack-ng/aircrack-ng)
    5. Cain & Abel
    6. Ophcrack

    AI recommended 6 alternatives but never named trustedsec/hate_crack. 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 trustedsec/hate_crack?
    pass
    AI named trustedsec/hate_crack explicitly

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

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

Subscribe to Pro for deep diagnoses

trustedsec/hate_crack — 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