registry / @mnemonik/cli / 7.164.0
@mnemonik/cli@7.164.0
⚠ Under reviewMnemonik installer and local project helper
AI Security Review
scanned 8d ago · by lpm-firewall-aiStatic inspection found no install-time trigger and the scanner evaluation matches WebAssembly glue. The exported credential-transfer helper’s callers and effective destination are unresolved, so its exposure cannot be classified from the inspected excerpts; manual review is appropriate.
Static reason
One or more suspicious static signals were detected.
Trigger
A runtime caller invokes the exported helper.
Impact
The recipient and purpose of the token transfer remain unresolved from the inspected source.
Mechanism
The helper posts the supplied body with the supplied token as a bearer authorization header to the supplied server and path.
AI rationale
Static inspection found no install-time trigger and the scanner evaluation matches WebAssembly glue. The exported credential-transfer helper’s callers and effective destination are unresolved, so its exposure cannot be classified from the inspected excerpts; manual review is appropriate.
Evidence
dist/runtime/signers.js
Decision evidence
public snapshotAI called this Manual Review at 57.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The CLI runs its bootstrap when invoked without help.
- A runtime helper sends a bearer token and JSON body to a server supplied as an argument.
- The helper is exported, but the inspected source does not establish who supplies the server or token.
- The scanner evaluation site is part of WebAssembly JavaScript glue that builds functions from module contents.
Evidence against
- The manifest has no lifecycle scripts, so installation alone does not trigger the CLI bootstrap.
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.164.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.164.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.