registry / @mnemonik/cli / 7.153.0
@mnemonik/cli@7.153.0
Mnemonik installer and local project helper
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest has no install lifecycle scripts, and source inspection did not confirm the scanner’s dynamic-code or command-execution flags as an attack path. The inspected update code fetches version metadata, while the signer helper’s caller and any unrelated credential destination were not established.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI or calling exported library functions.
Impact
No confirmed malicious impact or attack surface was established.
Mechanism
The CLI bootstraps on invocation; the inspected update code retrieves release metadata. No lifecycle hook or confirmed malicious credential transfer was found.
AI rationale
The manifest has no install lifecycle scripts, and source inspection did not confirm the scanner’s dynamic-code or command-execution flags as an attack path. The inspected update code fetches version metadata, while the signer helper’s caller and any unrelated credential destination were not established.
Evidence
package.jsondist/bin.jsdist/runtime/bootstrap.jsdist/runtime/selfUpdate.jsdist/runtime/signers.jsdist/install/journey.js
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 78.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares no lifecycle scripts and points to a CLI entrypoint and library module.
- The CLI invokes its bootstrap when run; the package manifest does not run it during installation.
- The flagged self-update path fetches latest-version metadata and caches it; inspected code does not show remote response code being executed.
- The signer helper posts JSON to a supplied server using a bearer token; no caller of this helper was found in the inspected signer file.
- The installer’s default API origin is api.mnemonik.dev, with an environment override.
- Scanner flags for eval and child-process use occur in bundled code; inspection did not establish a malicious execution or exfiltration path.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
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.153.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.153.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.