Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want agents to remember repo constraints, prior incidents, and architecture decisions across sessions without standing up external vector infrastructure.
Who should use it
Who should skip it
Move on from uudam42/agent-memory-engine if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
uudam42/agent-memory-engine is tracked by RepoRadar as an agent project in the Developer Tools section. First seen 2026-06-28; the source record was last checked on 2026-06-28. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, uudam42/agent-memory-engine is strongest on workflow potential (9.5) and open-source/build quality (8.4) and weakest on momentum (5.0) — 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 uudam42/agent-memory-engine record combines a 8.0/10 composite score with separate popularity (1.0), risk (conditional), 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
The first bootstrap writes agent-memory policy files into CLAUDE.md or .cursor/rules and creates a local .memory-engine knowledge store, so test it on one repository before rolling it across shared client profiles; It indexes code, docs, logs, and diffs into a searchable local store, so avoid pointing it at repositories whose source or incident history you cannot retain on disk in one place.