registry / codex-supermemory / 1.0.17
codex-supermemory@1.0.17
Persistent memory for OpenAI Codex CLI — powered by Supermemory
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package provides a Codex memory integration, with no install-time lifecycle hook. Its automatic session and prompt requests send data to the configured Supermemory service for the advertised recall feature; the scanner’s credential and execution flags are explained by that flow and project-tag setup.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user runs the CLI to install the integration; session and recall hooks then run as part of Codex sessions.
Impact
Prompts and project tags are sent to the Supermemory service for memory search, consistent with the package’s stated purpose. The update check contacts the npm registry.
Mechanism
Hooks use the package’s Supermemory API key and configured API base URL to retrieve memory context. The session hook also checks npm for a newer package version.
AI rationale
The package provides a Codex memory integration, with no install-time lifecycle hook. Its automatic session and prompt requests send data to the configured Supermemory service for the advertised recall feature; the scanner’s credential and execution flags are explained by that flow and project-tag setup.
Evidence
~/.codex/supermemory/credentials.json~/.codex/supermemory/.mark-tip-shown
Network endpoints3
api.supermemory.aiconsole.supermemory.ai/auth/connectregistry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and declares no install, preinstall, or postinstall lifecycle hook.
- The session hook starts browser authentication only when no Supermemory API key is configured.
- The bundled Supermemory client uses a Supermemory API key with the configured Supermemory base URL, defaulting to the vendor API.
- The session hook checks only the package’s latest version through the npm registry.
- The recall hook takes the prompt and project context for its advertised memory search feature.
Evidence against
- Session and recall hooks run automatically and may send prompts and project tags to Supermemory as part of the package’s core memory feature.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/hooks/recall.jsView file
177var import_node_crypto = require("node:crypto");
L178: var import_node_child_process = require("node:child_process");
L179: var import_node_fs3 = require("node:fs");
High
Child Process
Package source references child process execution.
dist/hooks/recall.jsView on unpkg · L177dist/cli.jsView file
413try {
L414: const utilInspect = eval("require('util').inspect");
L415: _custom = utilInspect.custom;
High
dist/hooks/mcp-proxy.jsView file
4// src/hooks/mcp-proxy.ts
L5: var import_node_readline = require("node:readline");
L6:
Findings
1 Critical4 High4 Medium4 Low
CriticalCredential Exfiltrationdist/hooks/session-start.js
HighChild Processdist/hooks/recall.js
HighEvaldist/cli.js
HighSame File Env Network Executiondist/hooks/session-start.js
HighSandbox Evasion Gated Capabilitydist/hooks/session-start.js
MediumDynamic Requiredist/hooks/mcp-proxy.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to codex-supermemory@1.0.17.
See all versions of codex-supermemory for other recorded verdicts.
- Review the evidence and your use of codex-supermemory@1.0.17 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.