RRepoGEO

REPOGEO REPORT · LITE

Clats97/ClatScope

Default branch main · commit d90538f5 · scanned 6/30/2026, 1:07:27 PM

GitHub: 1,494 stars · 211 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)

2 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 Clats97/ClatScope, 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 opening to explicitly state its core OSINT purpose

    Why:

    CURRENT
    ## ClatScope Info Tool & ClatScope Mini
    COPY-PASTE FIX
    ## ClatScope Info Tool: The Advanced OSINT Utility for Comprehensive Online Reconnaissance
  • highhomepage#2
    Add the project's homepage URL to the repository's 'About' section

    Why:

    COPY-PASTE FIX
    Add the official project homepage URL (e.g., `https://your-project-website.com`) to the 'About' section of your repository settings.
  • mediumreadme#3
    Add a clear statement about the project's license(s) to the README

    Why:

    COPY-PASTE FIX
    ## License
This project is licensed under [Specify License Name(s) Here, e.g., 'a custom license' or 'a combination of X and Y licenses']. Please refer to the `LICENSE` file for full details.

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 Clats97/ClatScope
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Maltego
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Maltego · recommended 2×
  2. SpiderFoot · recommended 2×
  3. theHarvester · recommended 2×
  4. Recon-ng · recommended 2×
  5. Shodan · recommended 2×
  • CATEGORY QUERY
    What are the best open-source intelligence tools for comprehensive online reconnaissance?
    you: not recommended
    AI recommended (in order):
    1. Maltego
    2. OSINT Framework
    3. SpiderFoot
    4. theHarvester
    5. Recon-ng
    6. Shodan
    7. GHunt

    AI recommended 7 alternatives but never named Clats97/ClatScope. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Need a versatile OSINT utility to retrieve geolocation, DNS, WHOIS, and data breach information.
    you: not recommended
    AI recommended (in order):
    1. Maltego
    2. SpiderFoot
    3. OSINT Framework (Website)
    4. Recon-ng
    5. theHarvester
    6. Shodan
    7. Have I Been Pwned (HIBP)

    AI recommended 7 alternatives but never named Clats97/ClatScope. 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 Clats97/ClatScope?
    pass
    AI named Clats97/ClatScope explicitly

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

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

Subscribe to Pro for deep diagnoses

Clats97/ClatScope — 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