registry / @mnemonik/cli / 7.170.2
@mnemonik/cli@7.170.2
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package has no install hooks, and its reviewed network behavior posts project context to the configured Mnemonik service. The scanner's eval use is tied to WebAssembly support code, with no evidence that it executes concealed remote responses.
Static reason
One or more suspicious static signals were detected.
Trigger
Explicit CLI or hook use; importing the entry point re-exports modules.
Impact
No credential theft, unrelated collection, or unrequested account action was identified.
Mechanism
The hook runtime sends project identity and repository fingerprint data to its configured service. The reported eval use constructs functions from WebAssembly module strings.
AI rationale
The package has no install hooks, and its reviewed network behavior posts project context to the configured Mnemonik service. The scanner's eval use is tied to WebAssembly support code, with no evidence that it executes concealed remote responses.
Network endpoints2
api.mnemonik.devconfigured hook server
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no lifecycle scripts or runtime dependencies.
- The import entry point re-exports CLI modules without directly invoking them; the binary runs the bootstrap when invoked.
- The flagged eval builds functions from WebAssembly module strings in generated Emscripten support code.
- Hook context posts a bounded project identity payload to its configured server using a bearer token; the payload contains hashes and project identifiers, not the token itself.
- The default API origin is api.mnemonik.dev, and the reported version change adds no lifecycle scripts or dependencies.
Evidence against
- The package includes dynamic evaluation and process execution in runtime code, but the inspected evaluation is part of WebAssembly support and git execution gathers repository metadata for hook context binding.
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 · 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.170.2.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.170.2 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.