registry / @mnemonik/cli / 7.139.5
@mnemonik/cli@7.139.5
Mnemonik installer and local project helper
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe scanner signals resolve to bundled WebAssembly helpers and ordinary Mnemonik API calls. Installation requires user action and consent, and the manifest has no lifecycle hooks.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the install command; no npm lifecycle hook triggers installation automatically.
Impact
No unconsented agent configuration change, credential disclosure, or remote code execution was established.
Mechanism
The installer requires affirmative consent for indexing and host changes. The flagged evaluation constructs helpers for the bundled WebAssembly module.
AI rationale
The scanner signals resolve to bundled WebAssembly helpers and ordinary Mnemonik API calls. Installation requires user action and consent, and the manifest has no lifecycle hooks.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts or runtime dependencies; the executable entrypoint is the CLI bootstrap.
- The agent-related source locations are scanner ignore-pattern comments. The installer requires consent for indexing and selected host changes, and noninteractive installs require explicit flags.
- The CLI updater verifies the release manifest and matches the package version and integrity before installing its own runtime.
- The reported evaluation sites construct helper functions from WebAssembly module data; Node loads the module from a file.
- Authentication requests send bearer tokens to the Mnemonik API resource selected for that authentication flow.
Evidence against
- Static alerts include dynamic evaluation and network access, but the inspected evaluation sites are WebAssembly helpers and the authentication calls target the Mnemonik API.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystem
Source & flagged code
7 flaggeddist/diagnostics.jsView file
898import { createHash, createPublicKey, randomUUID, timingSafeEqual, verify as verifySignature } from "node:crypto";
L899: import { execFile, execFileSync } from "node:child_process";
L900: function windowsCommand(file) {
High
Child Process
Package source references child process execution.
dist/diagnostics.jsView on unpkg · L8985213var func = `(${args}) => { ${body} };`;
L5214: ASM_CONSTS[start] = eval(func);
L5215: }
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 Critical5 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
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
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @mnemonik/cli@7.139.5.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.139.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.