registry / @mnemonik/cli / 7.170.7
@mnemonik/cli@7.170.7
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install hooks, and the flagged dynamic evaluation is part of WebAssembly scanner support. The inspected hook request sends hashed project context to the Mnemonik API and showed no credential exfiltration or unrelated account action.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI or invoking relevant scanner or hook functionality.
Impact
No malicious behavior identified in the inspected paths.
Mechanism
The scanner loads WebAssembly and its embedded glue; hook context sends project fingerprints to the configured Mnemonik API.
AI rationale
The manifest has no install hooks, and the flagged dynamic evaluation is part of WebAssembly scanner support. The inspected hook request sends hashed project context to the Mnemonik API and showed no credential exfiltration or unrelated account action.
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts or runtime dependencies; the package entry points are dist/bin.js and dist/index.js.
- The CLI invokes its bootstrap only when the executable is run; the package import entry re-exports modules.
- The flagged eval constructs JavaScript glue from strings in a WebAssembly module.
- In Node, the scanner language loader reads a supplied file path; its fetch branch is for non-Node environments.
- Hook context posts to the configured server and sends host/session identifiers plus device-root and repository fingerprints, not credential values.
Evidence against
- The package includes network and child-process code for its installer, scanner, and hook runtime.
- Hook context includes host and session identifiers and hashed project context in requests to the Mnemonik API.
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.170.7.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.170.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.