RRepoGEO

REPOGEO REPORT · LITE

PerryTS/perry

Default branch main · commit 9a3d2469 · scanned 6/24/2026, 9:41:59 PM

GitHub: 3,856 stars · 133 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
40 /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
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 PerryTS/perry, 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 statement to clearly state its core function

    Why:

    CURRENT
    # Perry

**One codebase. Every platform. Native performance.**

Perry is a native TypeScript compiler written in Rust. It takes your TypeScript and compiles it straight to native executables — no Node.js, no Electron, no browser engine. Just fast, small binaries that run anywhere.
    COPY-PASTE FIX
    **Perry: The Native TypeScript Compiler for Cross-Platform Executables**

Perry is a Rust-powered compiler that transforms your TypeScript directly into fast, small native executables for every platform — no Node.js, Electron, or browser runtime required.
  • mediumabout#2
    Update the 'About' description to be more explicit and benefit-oriented

    Why:

    CURRENT
    A native TypeScript compiler written in Rust. Compiles TypeScript directly to executables using SWC and LLVM.
    COPY-PASTE FIX
    Compile TypeScript directly to fast, small native executables for all platforms (Windows, macOS, iOS, Android, HarmonyOS, watchOS) using Rust, SWC, and LLVM, without Node.js or Electron.
  • mediumtopics#3
    Refine repository topics to include key terms and correct potential typos

    Why:

    CURRENT
    android, compile, harmonyos, ios, llvm, macos, native, smc, typescript, watchos, windows
    COPY-PASTE FIX
    android, compile, compiler, cross-platform, executable, harmonyos, ios, llvm, macos, native, rust, swc, typescript, watchos, windows

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 PerryTS/perry
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
pkg
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. pkg · recommended 2×
  2. Electron · recommended 1×
  3. Tauri · recommended 1×
  4. Neutralinojs · recommended 1×
  5. NW.js · recommended 1×
  • CATEGORY QUERY
    How to compile TypeScript code directly into a native executable for various platforms?
    you: not recommended
    AI recommended (in order):
    1. Electron
    2. Tauri
    3. Neutralinojs
    4. NW.js
    5. pkg
    6. Nexe
    7. NativeScript

    AI recommended 7 alternatives but never named PerryTS/perry. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a tool to build fast, small native binaries from TypeScript without Node.js runtime.
    you: not recommended
    AI recommended (in order):
    1. Bun
    2. Deno
    3. esbuild
    4. pkg
    5. nexe
    6. Rollup
    7. Terser
    8. tsc

    AI recommended 8 alternatives but never named PerryTS/perry. 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 PerryTS/perry?
    pass
    AI named PerryTS/perry explicitly

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

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

Subscribe to Pro for deep diagnoses

PerryTS/perry — 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