registry / codex-supermemory
codex-supermemory
Persistent memory for OpenAI Codex CLI — powered by Supermemory
This report shows the evidence for codex-supermemory@1.1.1. 0 of 10 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has no automatic npm lifecycle hook, and its Codex setup runs through an explicit CLI command. Runtime prompts and selected transcript content go to the configured Supermemory service for the package’s stated memory features; no unrelated credential collection or attack behavior was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user explicitly installs the Codex hooks; registered hooks then run on Codex session and prompt events.
Impact
Expected memory retrieval and sync for the user’s Codex projects.
Mechanism
Hooks retrieve relevant memory and can save selected transcript entries using the configured Supermemory service and credentials.
AI rationale
The package has no automatic npm lifecycle hook, and its Codex setup runs through an explicit CLI command. Runtime prompts and selected transcript content go to the configured Supermemory service for the package’s stated memory features; no unrelated credential collection or attack behavior was identified.
Evidence
~/.codex/supermemory/~/.codex/hooks.json~/.codex/config.toml~/.codex/skills/
Network endpoints1
api.supermemory.ai
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install, preinstall, or postinstall lifecycle scripts.
- The CLI performs setup only when invoked with the explicit install subcommand.
- The default service is https://api.supermemory.ai, and the authenticated fetch wrapper restricts bearer-token requests to the configured service origin and base path.
- The hooks use prompts and selected transcript entries for the package’s stated memory and recall features; the installer discloses automatic session and prompt recall.
Evidence against
- The session and prompt hooks send user-provided prompts and selected conversation content to the configured Supermemory service, as expected for a persistent-memory package.
- The CLI writes hook and skill files and updates Codex configuration when its explicit install command is run.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
6 flaggeddist/hooks/recall.jsView file
494var import_node_crypto2 = require("node:crypto");
L495: var import_node_child_process = require("node:child_process");
L496: var import_node_fs2 = require("node:fs");
High
Child Process
Package source references child process execution.
dist/hooks/recall.jsView on unpkg · L494dist/hooks/session-start.jsView file
61}
L62: await run("cmd.exe", ["/c", "start", '""', href]);
L63: return;
High
dist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = codex-supermemory@1.1.0
matchedIdentity = npm:Y29kZXgtc3VwZXJtZW1vcnk:1.1.0
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical3 High2 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/cli.js
HighChild Processdist/hooks/recall.js
HighShelldist/hooks/session-start.js
HighCross File Remote Execution Contextdist/cli.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowEvaldist/cli.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to codex-supermemory@1.1.1.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of codex-supermemory@1.1.1 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.