RRepoGEO

REPOGEO REPORT · LITE

cloudflare/workerd

Default branch main · commit 682dad1c · scanned 6/22/2026, 7:41:26 AM

GitHub: 8,341 stars · 657 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 cloudflare/workerd, 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
  • hightopics#1
    Add relevant topics to the repository

    Why:

    COPY-PASTE FIX
    javascript-runtime, wasm-runtime, serverless, edge-computing, http-proxy, cloudflare-workers, web-standards, v8-isolates, self-hosting
  • highreadme#2
    Clarify standalone nature and key use cases in the README's opening

    Why:

    CURRENT
    `workerd` (pronounced: "worker-dee") is a JavaScript / Wasm server runtime based on the same code that powers Cloudflare Workers.
    COPY-PASTE FIX
    `workerd` (pronounced: "worker-dee") is an open-source, self-hostable JavaScript / Wasm server runtime, built from the same code that powers Cloudflare Workers. It enables you to run serverless-like functions and build programmable HTTP proxies anywhere.
  • mediumcomparison#3
    Add a comparison section to the README

    Why:

    COPY-PASTE FIX
    Add a new section to the README, perhaps titled 'Comparison to other Runtimes' or 'Why workerd?', that outlines its differentiators from Node.js, Deno, Bun, Wasmtime, and other serverless platforms, focusing on its V8 isolates, web-standard APIs, and server-first design.

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 cloudflare/workerd
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Node.js
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Node.js · recommended 1×
  2. Deno · recommended 1×
  3. Bun · recommended 1×
  4. Cloudflare Workers · recommended 1×
  5. Wasmtime · recommended 1×
  • CATEGORY QUERY
    What server runtime supports JavaScript and WebAssembly for web-standard APIs?
    you: not recommended
    AI recommended (in order):
    1. Node.js
    2. Deno
    3. Bun
    4. Cloudflare Workers
    5. Wasmtime

    AI recommended 5 alternatives but never named cloudflare/workerd. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How can I self-host serverless-like functions or build an HTTP proxy with Wasm?
    you: not recommended
    AI recommended (in order):
    1. Fermyon Spin (fermyon/spin)
    2. Wasmtime (bytecodealliance/wasmtime)
    3. Extism (extism/extism)
    4. Envoy Proxy (envoyproxy/envoy)
    5. Suborbital Compute (suborbital/compute)
    6. Wasm Workers Server (vmware-labs/wasm-workers-server)

    AI recommended 6 alternatives but never named cloudflare/workerd. 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 cloudflare/workerd?
    pass
    AI named cloudflare/workerd explicitly

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

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

Subscribe to Pro for deep diagnoses

cloudflare/workerd — 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