Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who want durable cross-session agent memory without handing the plain text to a hosted vendor memory store.
Who should use it
Who should skip it
Skip Gitlawb/memlawb if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
Gitlawb/memlawb is tracked by RepoRadar as a infrastructure tool in the AI Infrastructure 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. Gitlawb/memlawb leads on workflow potential (9.1) and open-source/build quality (8.4); its lowest signal is momentum (3.0), so factor that in before investing setup time. 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 Gitlawb/memlawb 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 2.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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It is still an agent memory system, which means the real risk moves to what you choose to store and how carefully you scope each namespace; Zero-knowledge storage removes provider plaintext visibility but does not save you from passphrase loss or bad local secret-handling practices; The hosted path is labeled beta, so use a disposable evaluation namespace before depending on it for important project state.