RRepoGEO

REPOGEO REPORT · LITE

PerryTS/perry

Default branch main · commit 8a7ea998 · scanned 5/14/2026, 9:27:54 AM

GitHub: 2,895 stars · 92 forks

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 paragraph to explicitly state its category and differentiate from common alternatives

    Why:

    CURRENT
    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 is a **native TypeScript compiler** that transforms your TypeScript code directly into fast, standalone executables for any platform. Unlike web-based solutions like Electron or runtimes like Node.js/Deno, Perry delivers truly native performance and tiny binaries, making it ideal for high-performance desktop GUIs and command-line tools.
  • mediumtopics#2
    Add more specific topics to improve category visibility

    Why:

    CURRENT
    compile, cranelift, smc, typescript
    COPY-PASTE FIX
    typescript-compiler, native-apps, cross-platform-desktop, rust-lang, llvm, swc
  • lowcomparison#3
    Add a dedicated section comparing Perry to common alternatives like Electron and Tauri

    Why:

    COPY-PASTE FIX
    ## Why Perry? (vs. Electron, Tauri, Node.js, Deno)
Perry compiles your TypeScript directly to native machine code, offering superior performance, smaller binary sizes, and zero runtime dependencies compared to web-based frameworks like Electron or Tauri, or JavaScript runtimes like Node.js and Deno. This means faster cold starts, lower memory usage, and a truly native user experience.

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
Electron
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Electron · recommended 2×
  2. Bun · recommended 1×
  3. Deno · recommended 1×
  4. pkg · recommended 1×
  5. Nexe · recommended 1×
  • CATEGORY QUERY
    How to compile TypeScript applications into fast, standalone native executables without Node.js?
    you: not recommended
    AI recommended (in order):
    1. Bun
    2. Deno
    3. pkg
    4. Nexe
    5. Electron
    6. GraalVM Native Image

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

    Show full AI answer
  • CATEGORY QUERY
    What are options for building cross-platform desktop GUIs using TypeScript with native performance?
    you: not recommended
    AI recommended (in order):
    1. Tauri
    2. Electron
    3. Neutralinojs
    4. Proton Native
    5. NW.js (Node-Webkit)
    6. Qt for WebAssembly

    AI recommended 6 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