registry / @mnemonik/cli / 7.141.2
@mnemonik/cli@7.141.2
Mnemonik installer and local project helper
AI Security Review
scanned 19d ago · by lpm-firewall-aiClean: package.json has no lifecycle scripts, and the flagged eval sites are generated Emscripten glue rather than remote-response execution. Updates verify signed manifests, while agent setup requires explicit consent flags.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when a user invokes the command; agent setup is an explicit CLI operation.
Impact
No unconsented install-time mutation, remote code execution, or credential transfer was established.
Mechanism
The bootstrap rejects dependencies with lifecycle scripts, and the updater verifies signed release manifests. Agent setup checks for consent flags before proceeding.
AI rationale
Clean: package.json has no lifecycle scripts, and the flagged eval sites are generated Emscripten glue rather than remote-response execution. Updates verify signed manifests, while agent setup requires explicit consent flags.
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no npm lifecycle scripts or runtime dependencies.
- The CLI runs its bootstrap when invoked; bootstrap rejects dependencies with preinstall, install, or postinstall scripts.
- Release updates verify a minisign signature and check package versions before accepting the manifest.
- The flagged eval sites are Emscripten glue that builds asm callbacks from module data, not code read from a remote response.
- The agent-target offsets describe scanner ignore-pattern comments, not agent settings writes.
- Agent setup requires explicit host, apply, and indexing consent flags when applicable.
Evidence against
- Static hints flag eval, network, and child-process use, but inspection tied the eval matches to bundled Emscripten glue and found no install hook.
- The signer helper takes its server and token as explicit parameters; no package caller exporting command output or saved credentials was found.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVars
Source & flagged code
8 flaggeddist/diagnostics.jsView file
923import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L924: import { execFile, execFileSync } from "node:child_process";
L925: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L9235245var func = `(${args}) => { ${body} };`;
L5246: ASM_CONSTS[start] = eval(func);
L5247: }
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 Critical6 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
HighCommand Output Exfiltrationdist/runtime/signers.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
Affected versions and remediation
This report applies to @mnemonik/cli@7.141.2.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.141.2 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.