Item detail
github.com

aayoawoyemi/Ori-Mnemos

aayoawoyemi/Ori-Mnemos is a library in RepoRadar's Radar section, holding Silver tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 9.3 out of 10.

Score7.8
Popularity7.6
Risklow
TierSilver
Score breakdown
Usefulness8.0
Novelty9.0
Momentum7.0
Maturity5.8
Open-source/build8.4
Evidence7.2
Workflow potential9.3
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for AI agent builders, researchers, and self-hosters who want a local-first, markdown-on-disk persistent memory layer for AI agents with no database lock-in, so agents can remember, forget, and re-learn across sessions without uploading the knowledge graph to a vendor cloud or depending on a hosted memory SaaS.

Who should use it

AI agent builders who want a local-first persistent memory layer for agents with no vendor lock-in researchers who need an inspectable markdown-on-disk knowledge graph for agent memory experiments self-hosters who want Git-versioned agent memory instead of a hosted vector database open-source contributors who want an Apache-2.0 alternative to closed-source agent memory SaaS

Who should skip it

Skip aayoawoyemi/Ori-Mnemos if the source link, documentation, or setup requirements do not align with your current workflow or stack.

About this signal

aayoawoyemi/Ori-Mnemos is tracked by RepoRadar as a library in the Radar section. First seen 2026-06-21; the source record was last checked on 2026-06-21. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, aayoawoyemi/Ori-Mnemos is strongest on workflow potential (9.3) and novelty (9.0) and weakest on maturity (5.8) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The aayoawoyemi/Ori-Mnemos record combines a 7.8/10 composite score with separate popularity (7.6), risk (low), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

It is a local-first persistent memory layer where every byte of the user's knowledge graph lives on disk in markdown, so audit what is committed to the knowledge graph, review the activation decay + spreading activation parameters for any sensitive content before enabling auto-retrieval, and back up the markdown knowledge graph before any schema-level migration.

Evidence links
Closest alternatives / related signals
agent-memory knowledge-graph local-first markdown open-source apache-2.0
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

44 dated snapshots retained from 2026-06-21 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score7.8 current · +0.0 net
Repository momentum7.5 current · +0.5 net
GitHub stars (observed)319 current · +5 net
GitHub stars319 exact observation
Versionv0.6.1
Last release2026-07-29T02:32:09Z
Maintenanceactive
Current risklow
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineModel Context Protocol

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-137.87.5319lowtry nowactive
2026-08-127.87.0318lowtry nowactive
2026-08-117.87.5319lowtry nowactive
2026-08-107.87.8319lowtry nowactive
2026-08-097.87.5318lowtry nowactive
2026-08-087.87.5318lowtry nowactive
2026-08-077.89.0317lowtry nowactive
2026-08-067.87.0Not recordedlowtry nownot recorded
2026-08-057.87.0Not recordedlowtry nownot recorded
2026-08-047.89.0317lowtry nowactive
2026-08-037.89.0317lowtry nowactive
2026-08-027.89.0317lowtry nowactive

Why the record changed

stars changed

Stars changed: 318 → 319.

stars changed

Stars changed: 319 → 318.

stars changed

Stars changed: 318 → 319.

stars changed

Stars changed: 317 → 318.

version changed

Version changed: v0.6.0 → v0.6.1.

stars changed

Stars changed: 314 → 316.

version changed

Version changed: v0.5.0 → v0.6.0.