registry / @mnemonik/cli / 7.164.1
@mnemonik/cli@7.164.1
Mnemonik installer and local project helper
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed runtime behavior fits the package’s installer, scanner, and project helper functions. Static indicators alone did not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
User invokes the CLI or its exported runtime helpers.
Impact
No unconsented credential transfer, destructive action, or remote code execution was established.
Mechanism
The installer checks for acceptance flags before automatic setup; the reviewed hook-context sender uses caller-supplied server, token, and body values.
AI rationale
The manifest has no install lifecycle hook, and the reviewed runtime behavior fits the package’s installer, scanner, and project helper functions. Static indicators alone did not establish a concrete attack surface.
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts and exposes the CLI through dist/bin.js.
- Installation requires explicit acceptance flags before automatic setup proceeds, and readiness reporting uses the configured Mnemonik API origin.
- The hook-context helper sends a caller-provided body to a caller-provided server and derives project context from the selected project; no provider credential theft or unrelated recipient was established.
- The scanner eval calls reconstruct functions from its embedded WebAssembly module; inspected source did not show remote response code reaching those sinks.
Evidence against
- The package contains dynamic code evaluation, child-process use, and network requests, but inspected contexts align with embedded WebAssembly, diagnostics, project setup, and Mnemonik service reporting.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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.164.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.164.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.