RRepoGEO

REPOGEO REPORT · LITE

WeaveMindAI/weft

Default branch main · commit 5ace657d · scanned 6/22/2026, 3:46:36 AM

GitHub: 1,563 stars · 176 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 WeaveMindAI/weft, 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

2 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Strengthen README's opening to clarify Weft's core identity as an AI orchestration language

    Why:

    CURRENT
    # Weft
    
    > **Building in public, two months in.** Weft is young. The language, the type system, and the durable executor are the stable parts. The node catalog is small and intentionally opinionated (a few dozen nodes across LLM, code, communication, flow, storage, and triggers). The long-term vision is to let projects define their own nodes fluently in the language itself, but that is still ahead. If you are evaluating it for production, treat it as a foundation to build on, not a finished product. Breaking changes are expected while the shape is still settling; they will be announced, and migration notes will come with them.
    >
    > **Note on the docs.** This README, `DESIGN.md`, `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, and most of the prose around the project were written fast to get the open source release out the door. They may sound a bit AI-generated in places. If you have the time and taste to rewrite any of them more cleanly, please do. A PR that improves the writing is as welcome as one that fixes a bug.
    
    **A programming language for AI systems.**
    
    In 2026, real software calls LLMs, spins up databases, waits for humans, browses the web, coordinates agents. Where are those primitives? You are still importing libraries and writing plumbing for things that should be one line.
    
    Weft is a language where LLMs, humans, APIs, and infrastructure are base ingredients. You wire them together, the compiler checks the architecture, and you get a visual graph of your program automatic
    COPY-PASTE FIX
    # Weft: A Programming Language for AI Orchestration
    
    Weft is a dedicated programming language designed for building and orchestrating complex AI systems. It treats LLMs, humans, APIs, and infrastructure as first-class primitives, allowing you to wire them together directly. The compiler checks your architecture, and you get an automatic visual graph of your program.
    
    > **Building in public, two months in.** Weft is young. The language, the type system, and the durable executor are the stable parts. The node catalog is small and intentionally opinionated (a few dozen nodes across LLM, code, communication, flow, storage, and triggers). The long-term vision is to let projects define their own nodes fluently in the language itself, but that is still ahead. If you are evaluating it for production, treat it as a foundation to build on, not a finished product. Breaking changes are expected while the shape is still settling; they will be announced, and migration notes will come with them.
    >
    > **Note on the docs.** This README, `DESIGN.md`, `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, and most of the prose around the project were written fast to get the open source release out the door. They may sound a bit AI-generated in places. If you have the time and taste to rewrite any of them more cleanly, please do. A PR that improves the writing is as welcome as one that fixes a bug.
  • mediumhomepage#2
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://weft.ai

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 WeaveMindAI/weft
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
langchain-ai/langchain
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. langchain-ai/langchain · recommended 1×
  2. run-llama/llama_index · recommended 1×
  3. deepset-ai/haystack · recommended 1×
  4. nodejs/node · recommended 1×
  5. microsoft/TypeScript · recommended 1×
  • CATEGORY QUERY
    What programming language helps orchestrate complex AI workflows involving LLMs and agents?
    you: not recommended
    AI recommended (in order):
    1. LangChain (langchain-ai/langchain)
    2. LlamaIndex (run-llama/llama_index)
    3. Haystack (deepset-ai/haystack)
    4. Node.js (nodejs/node)
    5. TypeScript (microsoft/TypeScript)
    6. LangChain.js (langchain-ai/langchainjs)
    7. Spring Boot (spring-projects/spring-boot)
    8. Deeplearning4j (deeplearning4j/deeplearning4j)
    9. .NET (dotnet/runtime)

    AI recommended 9 alternatives but never named WeaveMindAI/weft. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a framework for building robust AI applications that integrate LLMs, databases, and human steps.
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Haystack (deepset/Haystack)
    4. Microsoft Semantic Kernel
    5. DSPy
    6. OpenAI Assistants API
    7. FlowiseAI

    AI recommended 7 alternatives but never named WeaveMindAI/weft. 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 WeaveMindAI/weft?
    pass
    AI named WeaveMindAI/weft explicitly

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

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

Subscribe to Pro for deep diagnoses

WeaveMindAI/weft — 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