registry / @mnemonik/cli / 7.156.3
@mnemonik/cli@7.156.3
Mnemonik installer and local project helper
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook. The suspicious static matches inspected are consistent with scanner-generated glue and a parameterized helper; source inspection did not establish a reachable malicious behavior or unauthorized credential transfer.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI or invoking package runtime functionality.
Impact
No concrete malicious effect or unauthorized credential disclosure was established.
Mechanism
The scanner glue builds functions from its embedded scanner data. The HTTP helper posts a caller-provided body with a caller-provided bearer token to a caller-provided server.
AI rationale
The manifest has no install lifecycle hook. The suspicious static matches inspected are consistent with scanner-generated glue and a parameterized helper; source inspection did not establish a reachable malicious behavior or unauthorized credential transfer.
Decision evidence
public snapshotAI called this Clean at 82.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no lifecycle scripts, and its bin invokes the CLI bootstrap when run.
- The scanner eval constructs functions from scanner glue data; this inspected code does not show execution of remote response text.
- The credential-bearing HTTP helper accepts its server, token, and body as arguments; no caller was found in the package search.
Evidence against
- Static hints flag generated eval code and a credential-bearing HTTP helper, but the inspected source does not establish a malicious execution or credential-transfer path.
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.156.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.156.3 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.