npm analyzed 3.102.0

mneme-ai

v3.102.0
npm

Mneme — the memory layer for your codebase. Knows the WHY, the WHAT, the WHERE-IT-BREAKS.

maintainer
mneme_npm
license
MIT
first seen
2026-05-22
last seen
2026-06-16
releases · 30d
426
short id
risk58/100 · heuristic grade
C elevated
  • capability exposureinferred+35
  • recent driftinferred+20
  • supply-chainattested+6
  • trust mitigatorsmixed−3

attestedinferredmixed

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.

graded 10m ago · see ecosystem CVEs →

risk trajectory4 movements
  • E · 82C · 58
  • C · 50E · 82
  • D · 74C · 50
  • C · 38D · 74
capability exposuregrade factor +35
Inferred surface — each links to servers holding it:
vulnerabilities0 CVEs

no known CVEs for this server.

tool safetyall quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

skills & danger signalsnpm-tarball
prompt-surface shipped agent-instruction files + hidden-content / dangerous-code findings — quoted from the analyzed source

analyzed v3.102.0 · analyzer v17 · 2d ago

danger signals1

other grade factorsevidence elsewhere
embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:mneme-ai/badge.svg)](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.