memoryrouter-codex@1.4.0
Automatic, project-scoped MemoryRouter memory for OpenAI Codex
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no npm install lifecycle hook, and its configuration changes require an explicit CLI command. Its automatic hooks, remote content transfer, and server-instructed detached Codex execution warrant a warning rather than a block.
Decision evidence
public snapshot- The explicit init command writes Codex MCP, hook, and AGENTS configuration.
- Installed hooks automatically start a detached background consolidation process when the API reports a suggestion.
- The background flow passes server-provided reflection instructions to `codex exec`.
- The runtime sends prompts and completed assistant messages to the MemoryRouter API when hooks are enabled.
- package.json contains no preinstall, install, or postinstall lifecycle hook.
- Control-surface changes require the user to run `memoryrouter-codex init`; hooks and AGENTS changes can be disabled.
- The project MCP command pins the same package version rather than selecting an older release.
- No credential harvesting, obfuscated payload, or unrelated network endpoint was found.
Source & flagged code
5 flaggedPackage source references child process execution.
runtime/project.cjsView on unpkg · L4A single source file combines environment access, network access, and code or shell execution; review context before blocking.
lib/installer.cjsView on unpkg · L124Manifest-trigger-reachable source writes behavior-bearing configuration into a user or project AI-agent control surface.
lib/installer.cjsView on unpkgThe explicit init command writes Codex MCP, hook, and AGENTS configuration.
lib/installer.cjsView on unpkg · L64This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/cli.cjsView on unpkgFindings
Affected versions and remediation
This report applies to memoryrouter-codex@1.4.0.
See all versions of memoryrouter-codex for other recorded verdicts.
- Review the evidence and your use of memoryrouter-codex@1.4.0 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.