Score7.7
Popularity88.0
Riskconditional
TierSilver
Score breakdown
Usefulness8.0
Novelty9.0
Momentum7.0
Maturity7.4
Open-source/build8.4
Evidence8.0
Workflow potential9.2
Setup ease8.8
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI agent authors who want a **local-first** memory substrate that runs on a single SQLite file with FTS5 search — no vector store, no embeddings, no retrieval model, no external infrastructure — and the agent runs on a 4 vCPU / 16 GB box; for engineering teams that need **multi-tenant by design** — the schema enforces `UNIQUE (tenant_id, category, name)` at the SQLite level so two agent
Who should use it
AI agent authors who want a **local-first** memory substrate that runs on a single SQLite file with FTS5 search — no vector store, no embeddings, no retrieval model, no external infrastructure — and the agent runs on a 4 vCPU / 16 GB boxEngineering teams that need **multi-tenant by design** — the schema enforces `UNIQUE (tenant_id, category, name)` at the SQLite level so two agents cannot stomp each other's WARM entitiesEngineering teams that need a **rule-enforced single source of truth per entity** — Rule 43 is enforced at the schema level, not just by convention in the application code, and drift is impossible by constructionEngineering teams that want **append-only audit trail** — the COLD journal tier is append-only by schema, ARCHIVE keeps retired entities for audit, REFERENCE is for static knowledge that rarely changes, HOT is the live working state rewritten in place**Hermes Agent v0.13+** users — `pip install sibyl-memory-hermes && sibyl-memory-hermes install-plugin` and edit `~/.hermes/config.yaml` with `memory: {provider: sibyl}`MCP-compatible agent users (Claude Code, Codex, Cursor, Continue) — `pip install sibyl-memory-mcp` and point any MCP client at the bundled server entry pointUsers who care about **privacy disclosure** — the README is explicit that memory content never leaves the machine, the only outbound network call is tier verification (account id, session token, DB byte size, proposed delta — never the memory contents), and free unactivated use makes no network calls at allEngineering teams evaluating research-vs-production — the 95.6% LongMemEval Oracle score is self-reported and the blog explicitly notes 'no official leaderboard exists, judges and generator models vary across entries,' but the architecture is the only file-based system in the top tier of the community leaderboardEngineering teams that want a **linter** to surface common architectural smells (unbounded HOT writes, duplicate WARM entities) — the memory linter is part of the activated path**Vendor-API-key-prerequisite caveat (cycle 164 pattern)**: the **free, unactivated path** makes no network calls and runs entirely local — this is the right starting surface for evaluation; the **activated path** binds a wallet or email and writes credentials to `~/.sibyl-memory/credentials.json`; the **staker / subscription tiers** unlock self-learning skill detection, the memory linter, and remove the local cap; if you need those features the OSS substrate is clean MIT but the activated path ties the memory engine to a Sibyl-controlled SaaS tier-check endpointEvaluation: `pip install sibyl-memory-cli && sibyl init` is the install path; for the Hermes Agent integration: `pip install sibyl-memory-hermes && sibyl-memory-hermes install-plugin`; for direct SDK use: `pip install sibyl-memory-client`; for MCP exposure: `pip install sibyl-memory-mcp`; the free unactivated tier is the right starting surface
Who should skip it
Skip Sibyl-Labs/Sibyl-Memory unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
Sibyl-Labs/Sibyl-Memory is tracked by RepoRadar as a local-first sqlite+fts5 agent-me in the MIT local-first agent-memory family (4 PyPI pack section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'try now' with a Silver tier and easy setup difficulty. Across RepoRadar's eight signals, Sibyl-Labs/Sibyl-Memory is strongest on workflow potential (9.2) and novelty (9.0) and weakest on momentum (7.0) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Sibyl-Labs/Sibyl-Memory a composite score of 7.7 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 88.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
free unactivated path makes no network calls; activated path binds a wallet or email to ~/.sibyl-memory/credentials.json and uses a vendor-controlled tier-check endpoint at api.sibyllabs.org; staker/subscription tiers required for self-learning skill detection; memory linter.
Evidence links
Closest alternatives / related signals
sibyl-memorysibyl-labslocal-firstsqlitefts5no-vectorsno-embeddingsno-retrieval-model
