registry / @mnemonik/cli / 7.171.0
@mnemonik/cli@7.171.0
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install hooks, and the CLI’s reviewed execution paths fit its installer, scanner, and project-context functions. The flagged evaluation is generated WebAssembly glue; the hook request sends context identifiers and hashes to its supplied server, with no evidence of credential exfiltration or unrelated execution.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when a user invokes the command; hook-context binding runs when called by the host integration.
Impact
No credential theft, unrelated code execution, or unsolicited account action was established.
Mechanism
The scanner loads data as WebAssembly and creates runtime glue from module exports. Hook context is posted to a caller-supplied server with hashed context identifiers.
AI rationale
The manifest has no install hooks, and the CLI’s reviewed execution paths fit its installer, scanner, and project-context functions. The flagged evaluation is generated WebAssembly glue; the hook request sends context identifiers and hashes to its supplied server, with no evidence of credential exfiltration or unrelated execution.
Network endpoints1
api.mnemonik.dev (default API origin in dist/install/journey.js)
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts or runtime dependencies.
- The CLI runs its bootstrap when the user invokes the `mnemonik` command; the package import entry re-exports modules.
- The scanner compiles fetched data as WebAssembly; its `eval` calls build JavaScript glue from strings exposed by the WebAssembly module.
- The hook context sender posts to a server passed into the function and includes host/session identifiers and hashed device and repository context.
- The Git remote fingerprint is a SHA-256 hash of a canonicalized remote, not the raw remote URL.
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.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.171.0 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.