registry / @mnemonik/cli / 7.163.0
@mnemonik/cli@7.163.0
⚠ Under reviewMnemonik installer and local project helper
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the CLI entrypoint starts its bootstrap only when invoked. The exported authenticated request helper has unresolved caller and credential-flow context, so I cannot verify its activation or recipient from the inspected source.
Static reason
One or more suspicious static signals were detected.
Trigger
Unknown; the helper is exported from its module, and the reviewed CLI entrypoint does not establish that it is called.
Impact
The source inspected does not establish whether a saved credential is exposed or whether the recipient is unrelated.
Mechanism
The helper posts JSON to the supplied server and attaches the supplied token as a bearer authorization header.
AI rationale
The manifest has no lifecycle scripts, and the CLI entrypoint starts its bootstrap only when invoked. The exported authenticated request helper has unresolved caller and credential-flow context, so I cannot verify its activation or recipient from the inspected source.
Decision evidence
public snapshotAI called this Manual Review at 63.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json declares no lifecycle scripts and points the command to dist/bin.js.
- dist/runtime/signers.js defines an HTTP helper that posts a caller-provided body to a caller-provided server with a bearer token.
- The helper appears as an export in dist/runtime/signers.js, but the inspected source does not identify its caller or establish the token’s origin and destination.
Evidence against
- The CLI entrypoint invokes bootstrap from the command line; the inspected source does not show the helper being activated by package installation or by the CLI entrypoint.
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.163.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.163.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.