registry / codex-supermemory / 1.0.21
codex-supermemory@1.0.21
Persistent memory for OpenAI Codex CLI — powered by Supermemory
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected credential handling is part of the package’s Supermemory client flow. Scanner indicators such as eval and network use did not establish malicious behavior in the reviewed source.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The CLI or its Codex hooks run during ordinary user-invoked use.
Impact
No concrete malicious effect or unrelated credential recipient was established.
Mechanism
The client reads the package’s Supermemory credential and sends service requests to its configured base URL, which defaults to api.supermemory.ai.
AI rationale
The manifest has no install lifecycle hook, and inspected credential handling is part of the package’s Supermemory client flow. Scanner indicators such as eval and network use did not establish malicious behavior in the reviewed source.
Evidence
~/.codex/supermemory/credentials.json
Network endpoints2
api.supermemory.aiconsole.supermemory.ai/auth/connect
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines the CLI entrypoint and has no install lifecycle hook; its scripts are build, typecheck, and test.
- The CLI and hook files read Supermemory credentials from the package’s named credentials file and use the configured Supermemory service URL.
- The session hook client passes the Supermemory API key and base URL to the Supermemory client; the default API host is api.supermemory.ai.
- The inspected hooks and services share the same Supermemory credential location and auth configuration; no unrelated recipient or concrete attack behavior was identified.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/hooks/recall.jsView file
212var import_node_crypto = require("node:crypto");
L213: var import_node_child_process = require("node:child_process");
L214: var import_node_fs3 = require("node:fs");
High
Child Process
Package source references child process execution.
dist/hooks/recall.jsView on unpkg · L212dist/hooks/session-start.jsView file
40// src/services/auth.ts
L41: var import_node_http = require("node:http");
L42: var import_node_fs = require("node:fs");
...
L50: // src/services/openUrl.ts
L51: var import_node_child_process = require("node:child_process");
L52: function run(command, args) {
...
L64: }
L65: if (process.platform === "win32") {
L66: try {
...
L70: }
L71: await run("cmd.exe", ["/c", "start", '""', href]);
L72: return;
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/hooks/session-start.jsView on unpkg · L4070
Findings
1 Critical5 High3 Medium4 Low
CriticalCredential Exfiltrationdist/hooks/session-start.js
HighChild Processdist/hooks/recall.js
HighShelldist/hooks/session-start.js
HighEvaldist/cli.js
HighSame File Env Network Executiondist/hooks/session-start.js
HighSandbox Evasion Gated Capabilitydist/hooks/session-start.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.21.
See all versions of codex-supermemory for other recorded verdicts.
- Review the evidence and your use of codex-supermemory@1.0.21 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.