registry / @mnemonik/cli / 7.173.1
@mnemonik/cli@7.173.1
Mnemonik installer and local project helper
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package has no install lifecycle scripts, and its CLI bootstrap runs on command invocation. Reviewed network and dynamic-evaluation behavior fits its installer and scanner functionality; no malicious data flow was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when a user invokes the command; installer reporting occurs during setup.
Impact
No malicious impact identified in the reviewed flows.
Mechanism
The installer reports readiness to the Mnemonik API, and the hook helper constructs hashed project context for a configured service.
AI rationale
The package has no install lifecycle scripts, and its CLI bootstrap runs on command invocation. Reviewed network and dynamic-evaluation behavior fits its installer and scanner functionality; no malicious data flow was identified.
Network endpoints1
api.mnemonik.dev/api/v1/install-sessions/current
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts or runtime dependencies.
- The CLI runs its bootstrap when the user invokes the command; the package entry point exports modules.
- The flagged eval builds JavaScript bridge functions from WebAssembly module data.
- The hook context helper sends a host session and project-root and repository hashes, not raw credentials.
- The installer reports readiness to its Mnemonik install-session endpoint.
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 · 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.173.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.173.1 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.