RRepoGEO

REPOGEO REPORT · LITE

tursodatabase/agentfs

Default branch main · commit 3a5ed2b8 · scanned 5/17/2026, 1:51:50 AM

GitHub: 3,121 stars · 170 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 tursodatabase/agentfs, 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 README's initial description for AI agent specialization

    Why:

    CURRENT
    <p align="center">
      The filesystem for agents.
    </p>
    COPY-PASTE FIX
    <p align="center">
      A specialized, persistent filesystem for AI agent state, memory, and tool interactions.
    </p>
  • highlicense#2
    Add a recognizable LICENSE file

    Why:

    COPY-PASTE FIX
    Create a LICENSE file in the repository root containing the standard MIT license text, consistent with the existing badge in the README.
  • mediumtopics#3
    Expand repository topics with specific AI agent storage terms

    Why:

    CURRENT
    agents, filesystem, sqlite, turso
    COPY-PASTE FIX
    ai-agents, agent-memory, agent-state, persistent-storage, virtual-filesystem, fuse, nfs, sqlite, turso, llm-agents

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 tursodatabase/agentfs
Avg rank
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
SQLite
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. SQLite · recommended 2×
  2. PostgreSQL · recommended 1×
  3. Redis · recommended 1×
  4. MongoDB · recommended 1×
  5. Cassandra · recommended 1×
  • CATEGORY QUERY
    What are the best persistent storage options for managing AI agent state and data?
    you: not recommended
    AI recommended (in order):
    1. PostgreSQL
    2. Redis
    3. MongoDB
    4. Cassandra
    5. Elasticsearch
    6. SQLite

    AI recommended 6 alternatives but never named tursodatabase/agentfs. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a dedicated file system abstraction for AI agent memory and contextual data.
    you: not recommended
    AI recommended (in order):
    1. ChromaDB
    2. Pinecone
    3. Weaviate
    4. Faiss
    5. Hugging Face Datasets library
    6. Apache Parquet
    7. SQLite

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

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

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

Subscribe to Pro for deep diagnoses

tursodatabase/agentfs — 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