registry / memoryrouter-codex / 1.8.1
memoryrouter-codex@1.8.1
Automatic MemoryRouter memory for OpenAI Codex: one vault shared by every session, repo and tool, including Claude Code
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and its Codex configuration changes occur through the explicit `init` command. Its runtime sends conversation content to MemoryRouter for the advertised memory feature; the reviewed credential and process flows serve that purpose.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs `memoryrouter-codex init`, then Codex hooks run during sessions; automatic consolidation can start when the service reports a suggestion.
Impact
Conversation content is processed by the package's stated memory service, and consolidation may invoke the user's Codex CLI. The reviewed behavior is disclosed and serves the package's purpose.
Mechanism
Hooks send prompts and final assistant responses to the MemoryRouter service for recall and storage. Consolidation uses retrieved memories with Codex, then submits the resulting entries to MemoryRouter.
AI rationale
The package has no install lifecycle hook, and its Codex configuration changes occur through the explicit `init` command. Its runtime sends conversation content to MemoryRouter for the advertised memory feature; the reviewed credential and process flows serve that purpose.
Evidence
~/.codex/config.toml~/.codex/hooks.json~/.codex/AGENTS.md~/.memoryrouter/codex/config.json~/.memoryrouter/consolidate.lock~/.memoryrouter/consolidate-state.json~/.memoryrouter/consolidate.log
Network endpoints3
api.memoryrouter.aimcp.memoryrouter.aiauth.memoryrouter.ai
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest declares no install, preinstall, or postinstall lifecycle script.
- Writes to Codex configuration and agent instructions run through the explicit `init` command.
- The package describes its hooks as saving the user's message and final response to MemoryRouter; it excludes tool calls and output.
- Runtime API requests send the configured key to the MemoryRouter API base.
- Automatic consolidation reuses the package's reflection flow and invokes Codex with retrieved memories.
Evidence against
- Hooks automatically capture conversation content after setup, but this is disclosed and central to the package's stated memory feature.
- The package uses child processes for Git identity lookup and Codex-based consolidation; the reviewed paths tie these actions to project labeling and the memory feature.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
6 flaggedruntime/project.cjsView file
29const crypto = require('crypto');
L30: const { execFileSync } = require('child_process');
L31:
High
Child Process
Package source references child process execution.
runtime/project.cjsView on unpkg · L29lib/installer.cjsView file
174L175: function codexInfo(cwd, env = process.env) {
L176: try {
L177: const output = execFileSync('codex', ['--version'], { cwd, env, encoding: 'utf8', timeout: 5000 }).trim();
L178: return { installed: true, output, version: parseVersion(output) };
...
L185: try {
L186: const response = await fetch(url, { ...init, signal: controller.signal });
L187: let data = null;
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
lib/installer.cjsView on unpkg · L174•Manifest-trigger-reachable source links an external AI-agent control path to a behavior-bearing write operation.
'use strict';
const fs = require('fs');
const os = require('os');
const path = require('path');
const { execfilesync } = require('child_process');
const { codexhome, datahome, loadconfig, saveconfig, configpath, getapikey, apikeysource } = require('../runtime/config.cjs');
const { resolveproject } = require('../runtime/project.cjs');
const { mcp_endpoint, integration_version } = require('../runtime/constants.cjs');
const {
installtoml, uninstalltoml, installagents, uninstallagents, readtext, replaceblock,
hasunmanagedmemoryroutertable, externalremoteservername, toml_start, toml_end, agents_start, agents_end,
} = require('./managed.cjs');
const { installhooks, uninstallhooks
Findings
4 High2 Medium6 Low
HighChild Processruntime/project.cjs
HighSame File Env Network Executionlib/installer.cjs
HighTrigger Reachable External Ai Agent Control Surface Mutationlib/installer.cjs
HighPrevious Version Dangerous Deltabin/cli.cjs
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencebin/cli.cjs
Affected versions and remediation
This report applies to memoryrouter-codex@1.8.1.
See all versions of memoryrouter-codex for other recorded verdicts.
- Review the evidence and your use of memoryrouter-codex@1.8.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.