Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for coding-agent users who want durable project memory, cross-session recall, and smaller context payloads without locking long-term context inside one vendor's chat archive.
Who should use it
Who should skip it
Avoid running NeoLi00/memX in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
NeoLi00/memX is tracked by RepoRadar as a tool in the AI Memory section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, NeoLi00/memX is strongest on workflow potential (9.5) and maturity (9.1) and weakest on setup ease (6.4) — 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 NeoLi00/memX a composite score of 8.4 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 426.0 and never affects the composite score or tier. The risk label of 'medium' 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
memX stores durable project memory and can inject prior evidence into later sessions, so teams should decide up front what code, prompts, and task history are acceptable to retain locally; Quickstart installs native lifecycle hooks, local plugin marketplace files, and a managed background service, so it should be tested in one repo before being rolled out across a broader workstation setup; Using hosted providers for memory compilation or recall planning still routes selected context through those providers, so sensitive projects should review which model endpoint is backing the service.