RRepoGEO

REPOGEO REPORT · LITE

evilsocket/nerve

Default branch main · commit 3c8b9c35 · scanned 5/27/2026, 11:22:01 PM

GitHub: 1,321 stars · 113 forks

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 evilsocket/nerve, 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 disambiguation statement to the README

    Why:

    COPY-PASTE FIX
    Add the following sentence immediately after the main description in the README: "Note: This project, `evilsocket/nerve`, is an Agent Development Kit for LLM-based agents and is distinct from other projects sharing the 'nerve' name (e.g., for service discovery)."
  • highhomepage#2
    Set the repository homepage URL

    Why:

    COPY-PASTE FIX
    Set the `homepage` URL in the repository settings to `https://github.com/evilsocket/nerve/blob/main/docs/index.md` (or a dedicated project website if one exists).
  • mediumlicense#3
    Clarify the project's license in the README

    Why:

    COPY-PASTE FIX
    Add a section to the README (e.g., under 'About' or 'Contributing') stating: "This project is licensed under the terms detailed in the `LICENSE.md` file."

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 evilsocket/nerve
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LangChain
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. LangChain · recommended 2×
  2. LlamaIndex · recommended 2×
  3. CrewAI · recommended 2×
  4. Marvin · recommended 2×
  5. Autogen · recommended 1×
  • CATEGORY QUERY
    How can I declaratively define and run LLM-based agents using simple configuration files?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. CrewAI
    4. Autogen
    5. Marvin

    AI recommended 5 alternatives but never named evilsocket/nerve. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are the best frameworks for orchestrating AI agents with custom tools and shell commands?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Haystack
    4. AutoGPT
    5. BabyAGI
    6. SuperAGI
    7. CrewAI
    8. Open Interpreter
    9. Marvin

    AI recommended 9 alternatives but never named evilsocket/nerve. 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 evilsocket/nerve?
    pass
    AI named evilsocket/nerve explicitly

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

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

Subscribe to Pro for deep diagnoses

evilsocket/nerve — 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