| FMRS | 66 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 15 / 20 | 16 / 20 |
|---|
| Maintenance | 14 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Development teams that want shared project memory across different AI coding tools.
- Experienced developers who frequently start new sessions and lose context.
- Projects that value preserving design decisions and reasoning.
- Users who prefer local-first, privacy-friendly memory storage.
- Users working with multiple MCP-compatible agents who want a unified memory layer.
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Simple projects that only need single-session memory.
- Users without Node.js or Git environments.
- Teams needing cloud sync or centralized memory management (Memorix is local-first).
- Users needing fully automatic, review-free long-term memory (long-term memory requires manual candidates and approval).
- Beginners who are configuration-sensitive, as setup involves multiple steps.
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Read and write local files (project root and memorix data directory).
- Execute Git commands (e.g., commit history reading).
- Start local HTTP services (if background mode is enabled).
- Optional API keys for LLM generation and embeddings (e.g., OpenAI, OpenRouter).
- Install agent plugins, rules, hooks, and skills (via setup command).
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Local-first means memory is not synced to cloud; you must back it up yourself.
- Misconfigured API keys may send data to third parties; ensure keys are secure.
- Hooks may consume computational resources or impact performance.
- Long-term memory requires human review, otherwise incorrect information may accumulate.
- Orchestration may create multiple worktrees or branches, requiring careful merge conflict resolution.
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Code, Codex, Cursor, Windsurf, Gemini CLI, GitHub Copilot CLI, Antigravity, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Kiro, OpenCode, Trae | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 20 | 19 |
|---|