RRepoGEO

REPOGEO REPORT · LITE

Zewo/Venice

Default branch master · commit 3e78449d · scanned 5/29/2026, 1:31:51 AM

GitHub: 1,495 stars · 57 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 Zewo/Venice, 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
    Add a clear statement about the project's maintenance status to the README

    Why:

    COPY-PASTE FIX
    Note: This project is no longer actively maintained. It serves as a historical example of structured concurrency and CSP for Swift.
  • mediumreadme#2
    Reposition the README's opening sentence to be more descriptive of its unique approach

    Why:

    CURRENT
    Venice provides structured concurrency and CSP for Swift.
    COPY-PASTE FIX
    Venice is a Swift library that provided a Go-like model for structured concurrency and CSP (Communicating Sequential Processes) using lightweight user-space threads (fibers/coroutines), wrapping a fork of the C library libdill.
  • lowtopics#3
    Add 'archived' or 'legacy' to the repository topics

    Why:

    CURRENT
    coroutines, csp, fibers, green-threads, linux, non-blocking, performance, server, server-side-swift, structured-concurrency, swift, swiftpm, synchronous, venice
    COPY-PASTE FIX
    coroutines, csp, fibers, green-threads, linux, non-blocking, performance, server, server-side-swift, structured-concurrency, swift, swiftpm, synchronous, venice, archived

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 Zewo/Venice
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Swift Concurrency
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Swift Concurrency · recommended 2×
  2. apple/swift-async-algorithms · recommended 1×
  3. Combine · recommended 1×
  4. vapor/vapor · recommended 1×
  5. apple/swift-nio · recommended 1×
  • CATEGORY QUERY
    How to achieve structured concurrency and CSP in Swift for server applications?
    you: not recommended
    AI recommended (in order):
    1. Swift Concurrency
    2. swift-async-algorithms (apple/swift-async-algorithms)
    3. Combine
    4. Vapor (vapor/vapor)
    5. SwiftNIO (apple/swift-nio)

    AI recommended 5 alternatives but never named Zewo/Venice. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are options for green threads or fibers in Swift for high-performance I/O?
    you: not recommended
    AI recommended (in order):
    1. Swift Concurrency
    2. SwiftNIO
    3. Libdispatch
    4. Vapor

    AI recommended 4 alternatives but never named Zewo/Venice. 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 Zewo/Venice?
    pass
    AI named Zewo/Venice explicitly

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

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

Subscribe to Pro for deep diagnoses

Zewo/Venice — 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