registry / @mnemonik/cli / 7.139.7
@mnemonik/cli@7.139.7
Mnemonik installer and local project helper
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe static signals resolve to bundled Emscripten code and normal CLI operations. The package has no install hook, and the updater validates release integrity, so the source does not support a malicious verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
The executable runs when a user invokes the CLI; package.json defines no install lifecycle scripts.
Impact
No unauthorized effect was established; the inspected network, scanner, and host operations are part of the CLI's user-invoked functionality.
Mechanism
The flagged evaluation is bundled Emscripten glue, and the update path verifies release data rather than executing code from the metadata check.
AI rationale
The static signals resolve to bundled Emscripten code and normal CLI operations. The package has no install hook, and the updater validates release integrity, so the source does not support a malicious verdict.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts or runtime dependencies, and the mnemonik binary invokes bootstrap when the user launches it.
- The flagged eval is in bundled Emscripten glue that builds module bridge functions; the updater's automatic check fetches version metadata and directs the user to run an update.
- The updater verifies release versions and integrity. Bootstrap rejects downloaded packages that declare preinstall, install, or postinstall scripts.
- The required Claude-related locations contain scanner ignore-rule comments: they say .claude/rules.md remains indexed and only .claude/worktrees is suppressed; these locations do not describe agent configuration writes.
- The other required files expose install-session, authentication, preflight, host, repository-discovery, and scanner operations; the inspected code shows ordinary CLI functionality, not an install-time attack.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEval
Source & flagged code
7 flaggeddist/diagnostics.jsView file
898import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L899: import { execFile, execFileSync } from "node:child_process";
L900: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L8985213var func = `(${args}) => { ${body} };`;
L5214: ASM_CONSTS[start] = eval(func);
L5215: }
High
1import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
L2: var __create = Object.create;
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/diagnostics.jsView on unpkg · L1Findings
1 Critical5 High4 Medium4 Low
CriticalRemote Response Code Executiondist/runtime/selfUpdate.js
HighChild Processdist/diagnostics.js
HighEvaldist/diagnostics.js
HighSame File Env Network Executiondist/install/journey.js
HighSandbox Evasion Gated Capabilitydist/install/journey.js
HighCross File Remote Execution Contextdist/auth/credentials.js
MediumDynamic Requiredist/diagnostics.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @mnemonik/cli@7.139.7.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.139.7 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.