registry / @mnemonik/cli / 7.150.0
@mnemonik/cli@7.150.0
Mnemonik installer and local project helper
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe scanner’s dynamic evaluation and command execution matches do not establish malicious behavior in context. The inspected manifest and bootstrap show no install hook and verify release inputs before installation, so the package is assessed as clean.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the mnemonik CLI.
Impact
No confirmed unauthorized execution, credential disclosure, or destructive action was established.
Mechanism
The bootstrap checks the installed package and lockfile; release fetching uses HTTPS and the update path requires a signed release manifest.
AI rationale
The scanner’s dynamic evaluation and command execution matches do not establish malicious behavior in context. The inspected manifest and bootstrap show no install hook and verify release inputs before installation, so the package is assessed as clean.
Network endpoints1
registry.npmjs.org/%40mnemonik%2Fcli/
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 npm scripts or runtime dependencies, so it defines no install lifecycle hook.
- The CLI runs its bootstrap after invocation. The bootstrap checks the installed package and lockfile, requires HTTPS release sources, and rejects packages with preinstall, install, or postinstall scripts.
- The update path checks a signed release manifest before installing the fetched CLI release.
Evidence against
- Static matches for evaluation and command execution occur in bundled runtime files; the inspected matches do not establish execution of attacker supplied code or malicious command behavior.
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.150.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.150.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.