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 a agent memory in the Developer Tools section. It was first seen on 2026-06-28 and last updated 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 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 uudam42/agent-memory-engine a composite score of 8.0 out of 10, placing it in the Gold 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 1.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.
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.