registry / @mnemonik/cli / 7.146.2
@mnemonik/cli@7.146.2
Mnemonik installer and local project helper
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe source supports a warning for package-owned host installation behavior, while the reviewed evaluation code is bundled WebAssembly glue and no npm lifecycle hook is present. The excerpts do not establish a concrete attack, so blocking is not warranted.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI install flow.
Impact
It can change host installation state as part of setup; the inspected excerpts do not establish credential theft, remote code execution, or unrequested account actions.
Mechanism
The installer passes selected hosts and an install plan to the host installation flow and enables apply behavior.
AI rationale
The source supports a warning for package-owned host installation behavior, while the reviewed evaluation code is bundled WebAssembly glue and no npm lifecycle hook is present. The excerpts do not establish a concrete attack, so blocking is not warranted.
Evidence
dist/install/journey.js
Decision evidence
public snapshotAI called this Suspicious at 58.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package describes itself as an installer and local project helper and has no npm lifecycle scripts.
- The CLI invokes its bootstrap when run, and the installer journey applies a selected install plan through the install flow.
- The flagged evaluation code builds callbacks from WebAssembly module strings in bundled runtime glue.
Evidence against
- The reviewed installer behavior is activated through the CLI; the manifest has no automatic install hook.
- The inspected evaluation code does not establish execution of code fetched from a remote response.
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.146.2.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.146.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.