RRepoGEO

REPOGEO REPORT · LITE

henomis/lingoose

Default branch main · commit 96c51c0f · scanned 6/6/2026, 10:52:06 PM

GitHub: 835 stars · 75 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 henomis/lingoose, 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 project status statement in the README

    Why:

    CURRENT
    > [!IMPORTANT]
    > **Hey there, LinGoose friend 🪿**
    >
    > First of all, thank you for being here. LinGoose has been a fun journey and I am proud of what it became.
    >
    > The honest news: LinGoose is no longer under active development. Life got busy, the AI world moved fast, and I found myself wanting to build something new rather than patch something old.
    >
    > That something new is Phero 🐜, a Go framework built from the ground up for multi-agent AI systems. Same values, better foundation, a lot more ambition.
    >
    > LinGoose is not going anywhere. It will stay here, stable and available. But if you are starting something new, come join the ant colony.
    COPY-PASTE FIX
    Move the content of the `[!IMPORTANT]` block to a new 'Project Status' section at the end of the README, after all other feature descriptions and usage guides. This allows the project's capabilities to be presented first.
  • mediumreadme#2
    Enhance the 'What is LinGoose?' section with its core differentiator

    Why:

    CURRENT
    LinGoose is a Go framework for building awesome AI/LLM applications.<br/>
    
    LinGoose is modular** — You can import only the modules you need to build your application.
    LinGoose is an abstraction of features** — You can choose your preferred implementation of a feature and/or create your own.
    LinGoose is a complete solution** — You can use LinGoose to build your AI/LLM application from the ground up.
    COPY-PASTE FIX
    LinGoose is a Go framework for building awesome AI/LLM applications. It provides a **Go-native, idiomatic implementation of an LLM application development framework**, offering features similar to Python's LangChain or LlamaIndex (e.g., chains, agents, memory, tools, provider integrations) within the Go ecosystem.
    
    LinGoose is modular** — You can import only the modules you need to build your application.
    LinGoose is an abstraction of features** — You can choose your preferred implementation of a feature and/or create your own.
    LinGoose is a complete solution** — You can use LinGoose to build your AI/LLM application from the ground up.
  • lowtopics#3
    Add 'framework' and 'sdk' to repository topics

    Why:

    CURRENT
    ai, chatgpt, embeddings, go, golang, index, llm, openai, pinecone, pipeline, prompt, vector
    COPY-PASTE FIX
    ai, chatgpt, embeddings, go, golang, index, llm, openai, pinecone, pipeline, prompt, vector, framework, sdk

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 henomis/lingoose
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Go-LLM
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Go-LLM · recommended 1×
  2. LangChain Go · recommended 1×
  3. LocalAI · recommended 1×
  4. OpenAI Go Library · recommended 1×
  5. llama.cpp · recommended 1×
  • CATEGORY QUERY
    What is a good Go framework for building large language model applications?
    you: not recommended
    AI recommended (in order):
    1. Go-LLM
    2. LangChain Go
    3. LocalAI
    4. OpenAI Go Library
    5. llama.cpp
    6. Ollama

    AI recommended 6 alternatives but never named henomis/lingoose. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How can I integrate vector databases and LLM prompts in a Go application?
    you: not recommended
    AI recommended (in order):
    1. Weaviate
    2. weaviate/weaviate-go-client (weaviate/weaviate-go-client)
    3. openai-go/openai (openai-go/openai)
    4. google/generative-ai-go (google/generative-ai-go)
    5. Pinecone
    6. pinecone-io/go-pinecone (pinecone-io/go-pinecone)
    7. Qdrant
    8. qdrant/go-client (qdrant/go-client)
    9. Chroma
    10. amikos-tech/chroma-go (amikos-tech/chroma-go)
    11. PostgreSQL
    12. pgvector
    13. jackc/pgx (jackc/pgx)
    14. OpenAI's `text-embedding-ada-002`
    15. Google's `text-embedding-004`

    AI recommended 15 alternatives but never named henomis/lingoose. 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 henomis/lingoose?
    pass
    AI named henomis/lingoose explicitly

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

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

Subscribe to Pro for deep diagnoses

henomis/lingoose — 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