RRepoGEO

REPOGEO REPORT · LITE

peass-ng/CloudPEASS

Default branch main · commit 526ce06c · scanned 6/6/2026, 10:42:18 AM

GitHub: 637 stars · 76 forks

AI VISIBILITY SCORE
30 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 0 warn · 1 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 peass-ng/CloudPEASS, 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
  • highabout#1
    Add a concise repository description

    Why:

    COPY-PASTE FIX
    Your one-stop solution to find your permissions whenever you compromise a principal in a Red Team across major cloud platforms: Azure, GCP, and AWS, focusing on privilege escalation and accessing sensitive information.
  • hightopics#2
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    cloud-security, privilege-escalation, red-team, aws, azure, gcp, pentesting, security-assessment, post-exploitation, enumeration
  • highlicense#3
    Add a LICENSE file to the repository

    Why:

    COPY-PASTE FIX
    Choose and add a standard open-source license file (e.g., MIT, Apache-2.0, GPL-3.0) to the repository root.

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 peass-ng/CloudPEASS
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Wiz
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Wiz · recommended 1×
  2. Orca Security · recommended 1×
  3. Palo Alto Networks Prisma Cloud · recommended 1×
  4. Lacework · recommended 1×
  5. Tenable.cs · recommended 1×
  • CATEGORY QUERY
    How to identify privilege escalation paths and sensitive data access across AWS, Azure, and GCP?
    you: not recommended
    AI recommended (in order):
    1. Wiz
    2. Orca Security
    3. Palo Alto Networks Prisma Cloud
    4. Lacework
    5. Tenable.cs
    6. Microsoft Defender for Cloud
    7. Google Cloud Security Command Center

    AI recommended 7 alternatives but never named peass-ng/CloudPEASS. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools help enumerate and classify cloud permissions for red team security assessments?
    you: not recommended
    AI recommended (in order):
    1. CloudGoat (RhinoSecurityLabs/CloudGoat)
    2. Pacu (RhinoSecurityLabs/Pacu)
    3. BloodHound (BloodHoundAD/BloodHound)
    4. CloudHound (BloodHoundAD/CloudHound)
    5. PMapper (nccgroup/PMapper)
    6. ScoutSuite (nccgroup/ScoutSuite)
    7. Prowler (prowler-cloud/prowler)
    8. Steampipe (turbot/steampipe)
    9. AWS CLI
    10. Azure CLI
    11. gcloud CLI

    AI recommended 11 alternatives but never named peass-ng/CloudPEASS. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    fail

    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 peass-ng/CloudPEASS?
    pass
    AI named peass-ng/CloudPEASS explicitly

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

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

Subscribe to Pro for deep diagnoses

peass-ng/CloudPEASS — 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
peass-ng/CloudPEASS — RepoGEO report