registry / @mnemonik/cli / 7.145.2
@mnemonik/cli@7.145.2
Mnemonik installer and local project helper
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection supports normal CLI and installer behavior: the package has no lifecycle scripts, the bootstrap rejects lifecycle-enabled release packages, and flagged evaluation is part of WebAssembly glue. The reviewed agent integration locations describe scanner exclusions and do not establish agent configuration mutation or credential transfer.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI starts its bootstrap; installer and host changes are explicit CLI actions with consent checks.
Impact
The inspected behavior does not establish an attack surface or unauthorized changes.
Mechanism
The manifest has no lifecycle hooks. The inspected bootstrap rejects lifecycle-enabled release packages, while the evaluation excerpt constructs functions from WebAssembly module glue.
AI rationale
Source inspection supports normal CLI and installer behavior: the package has no lifecycle scripts, the bootstrap rejects lifecycle-enabled release packages, and flagged evaluation is part of WebAssembly glue. The reviewed agent integration locations describe scanner exclusions and do not establish agent configuration mutation or credential transfer.
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies the CLI entry point and has no lifecycle scripts or runtime dependencies.
- The flagged eval code is embedded WebAssembly glue; the installer checks release package metadata and rejects lifecycle hooks, and the CLI asks for consent before applying host changes.
- The inspected agent integration hints describe scanner exclusions for `.claude/worktrees/`; they do not show agent configuration writes or telemetry.
Evidence against
- The package contains dynamic evaluation and child process calls, but inspected excerpts do not establish remote code execution or an attack.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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.145.2.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.145.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.