Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for agent builders who want a more auditable and portable memory discipline than a hidden vector store, but do not want to stand up a full memory service just to test the workflow.
Who should use it
Who should skip it
Consider tinqiao-oss/engramory lower priority if you already have a working solution in this category.
About this signal
tinqiao-oss/engramory is tracked by RepoRadar as a file-based agent memory protocol in the Developer Tools section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. tinqiao-oss/engramory leads on open-source/build quality (8.4) and workflow potential (8.4); its lowest signal is momentum (4.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 tinqiao-oss/engramory a composite score of 7.6 out of 10, placing it in the Silver 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 project explicitly describes the hook enforcement as best-effort rather than a global write guard, so do not treat it as a reliable cross-tool memory policy yet; It assumes a single writer and serialized writes, which makes it a poor default for shared or heavily parallel agent setups without extra coordination.