RRepoGEO

REPOGEO REPORT · LITE

Janlaywss/cloud-code

Default branch master · commit b9c60437 · scanned 6/6/2026, 1:23:00 AM

GitHub: 523 stars · 850 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 Janlaywss/cloud-code, 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 README H1 and update repository description

    Why:

    CURRENT
    # Cloud-code 破解版
    Description: cloud-code
    COPY-PASTE FIX
    # Source Code Recovery from npm Packages (via Sourcemaps)
    Description: A tool and guide for recovering original TypeScript/TSX source code from published npm packages using sourcemaps.
  • hightopics#2
    Add specific topics to improve categorization

    Why:

    CURRENT
    (none)
    COPY-PASTE FIX
    source-map, typescript, javascript, npm, package-analysis, reverse-engineering, code-recovery
  • highlicense#3
    Add a LICENSE file and clarify licensing terms

    Why:

    CURRENT
    (no LICENSE file detected — the repo has no recognizable license)
    COPY-PASTE FIX
    Create a LICENSE file in the repository root. If the project is not intended for open-source distribution, clearly state the terms of use and any restrictions within this file or in the README.

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 Janlaywss/cloud-code
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
source-map-explorer
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. source-map-explorer · recommended 1×
  2. Browser Developer Tools · recommended 1×
  3. sourcemap-decode · recommended 1×
  4. webpack-bundle-analyzer · recommended 1×
  5. Source Maps · recommended 1×
  • CATEGORY QUERY
    How to recover original TypeScript source code from a published npm package using sourcemaps?
    you: not recommended
    AI recommended (in order):
    1. source-map-explorer
    2. Browser Developer Tools
    3. sourcemap-decode
    4. webpack-bundle-analyzer

    AI recommended 4 alternatives but never named Janlaywss/cloud-code. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What tools can decompile JavaScript bundles back to their original TypeScript files for analysis?
    you: not recommended
    AI recommended (in order):
    1. Source Maps
    2. Webpack Bundle Analyzer (webpack-contrib/webpack-bundle-analyzer)
    3. Terser (terser/terser)
    4. JSNice (sola-da/jsnice)
    5. TypeScript Compiler (microsoft/TypeScript)
    6. js-beautify.com
    7. deobfuscate.io

    AI recommended 7 alternatives but never named Janlaywss/cloud-code. 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 Janlaywss/cloud-code?
    pass
    AI named Janlaywss/cloud-code explicitly

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

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

Subscribe to Pro for deep diagnoses

Janlaywss/cloud-code — 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
Janlaywss/cloud-code — RepoGEO report