registry / @mnemonik/cli / 7.141.3
@mnemonik/cli@7.141.3
Mnemonik installer and local project helper
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection found no npm lifecycle hook or concrete unauthorized behavior. The evaluation matches resolve to embedded WebAssembly parser support, while the inspected network and process calls serve CLI features.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes an authentication, install, or update command; package installation alone has no lifecycle trigger.
Impact
The inspected source did not establish unrelated credential export or broad agent configuration changes.
Mechanism
Authentication uses a device flow with the configured API resource, and updates verify release signatures. The flagged evaluation calls are in embedded tree-sitter WebAssembly support.
AI rationale
Source inspection found no npm lifecycle hook or concrete unauthorized behavior. The evaluation matches resolve to embedded WebAssembly parser support, while the inspected network and process calls serve CLI features.
Network endpoints3
auth.mnemonik.aiapi.mnemonik.dev/registry.npmjs.org/%40mnemonik%2Fcli/
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json points to the CLI and library entrypoints and declares empty scripts and dependencies.
- The agent-related locations are scanner ignore-pattern entries; `.claude/worktrees/` is excluded, while the separate install command has consent gates.
- The repeated `eval` matches are in embedded `web-tree-sitter` WebAssembly glue that reads JavaScript strings from WebAssembly exports.
- The CLI update command uses the package registry and verifies a release signature before installing an update.
- The OAuth flow passes its configured API resource into device authorization and sends the resulting bearer to that same resource; the defaults are Mnemonik services.
- The cited runtime files use ESM loader setup, and the project setup helper launches Node with an argument array and shell disabled.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
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.141.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.141.3 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.