registry / @mnemonik/cli / 7.171.2
@mnemonik/cli@7.171.2
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the command entry runs the installer only when invoked. The flagged evaluation and network behavior fit the bundled scanner and project setup functionality; the reviewed code does not show a malicious payload or credential exfiltration.
Static reason
One or more suspicious static signals were detected.
Trigger
No install hook is configured. Installer behavior starts when the CLI is explicitly invoked; importing the package exposes modules.
Impact
No unauthorized credential collection, remote code execution, or other attack impact was identified.
Mechanism
The flagged eval belongs to bundled Emscripten WebAssembly glue. The reviewed Node loader reads WebAssembly from a file. The hook context helper sends scoped project context when called.
AI rationale
The manifest has no lifecycle scripts, and the command entry runs the installer only when invoked. The flagged evaluation and network behavior fit the bundled scanner and project setup functionality; the reviewed code does not show a malicious payload or credential exfiltration.
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines no lifecycle scripts; its executable is dist/bin.js and its import entry is dist/index.js.
- The CLI calls bootstrap only when invoked as a command; the import entry re-exports modules.
- The scanner’s flagged eval is in Emscripten glue, and the language loader handles WebAssembly; in Node it reads the module from a file.
- The hook context helper sends project and session context, including hashed root and repository fingerprints, rather than discovered credentials.
Evidence against
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 · L9235256var func = `(${args}) => { ${body} };`;
L5257: ASM_CONSTS[start] = eval(func);
L5258: }
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/scanner/service.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.171.2.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.171.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.