registry / @mnemonik/cli / 7.146.5
@mnemonik/cli@7.146.5
⚠ Under reviewMnemonik installer and local project helper
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected self-update flow verifies a signed release and package integrity. The remaining flagged runtime behavior was not sufficiently resolved to support a clean or malicious finding, so manual review is appropriate.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI may invoke its bootstrap and update paths.
Impact
The available source does not establish malicious behavior or rule out risk in the unresolved paths.
Mechanism
The inspected update path verifies release metadata and integrity; other flagged runtime code was not sufficiently resolved.
AI rationale
The manifest has no install hook, and the inspected self-update flow verifies a signed release and package integrity. The remaining flagged runtime behavior was not sufficiently resolved to support a clean or malicious finding, so manual review is appropriate.
Evidence
package.jsondist/runtime/selfUpdate.js
Network endpoints1
registry.npmjs.org/%40mnemonik%2Fcli/
Decision evidence
public snapshotAI called this Manual Review at 56.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest has no install lifecycle scripts and declares an empty dependency set.
- The CLI self-update checks registry metadata against a signed release manifest and verifies the package integrity before installing an update.
- The inspected updater excerpt does not resolve the flagged evaluation sites or every runtime path needed for a full assessment.
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 · 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.5.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.146.5 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.