Mneme — the memory layer for your codebase. Knows the WHY, the WHAT, the WHERE-IT-BREAKS.
- capability exposure inferred + 35
- supply-chain attested + 6
- trust mitigators mixed − 11
attested inferred mixed
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
grade last moved 1w ago · see ecosystem CVEs →
- C · 38 → B · 30
- C · 50 → C · 38
- C · 58 → C · 50
- E · 82 → C · 58
- C · 50 → E · 82
- D · 74 → C · 50
- C · 38 → D · 74
No known CVEs for this server.
- low dangerous code
env-secret-flows-to-network-js: A process environment value reaches a network call. Review whether it is a credential leaving the process; the ordinary API-wrapper shape (read a ke
- low dangerous code
env-secret-flows-to-network-js: A process environment value reaches a network call. Review whether it is a credential leaving the process; the ordinary API-wrapper shape (read a ke
analyzed v3.153.0 · analyzer v33 · 4w ago
danger signals1
- suspicious endpoint api.telegram.org package/dist/commands/live.js :1993
const tgReach = tgCfg ? await ping(`https://api.telegram.org/bot${tgCfg.token}/getMe`) : null;
- supply-chain +6 supply-chain hub →
[](https://mcpobservatory.com/servers/npm:mneme-ai/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of mneme_npm.