registry / @mnemonik/cli / 7.166.1
@mnemonik/cli@7.166.1
Mnemonik installer and local project helper
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the flagged dynamic evaluation is tied to the bundled Tree-sitter WebAssembly parser. The reviewed network behavior supports the installer and hook features; no credential theft, unrelated collector, or unrequested account action was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
Explicit CLI install or use of exported hook functionality; no install lifecycle script is configured.
Impact
No concrete malicious behavior was found in the reviewed paths.
Mechanism
Install-session readiness is sent to the package service. Hook context sends project and device hashes to a supplied server. The scanner eval is part of its bundled WebAssembly parser support.
AI rationale
The manifest has no lifecycle scripts, and the flagged dynamic evaluation is tied to the bundled Tree-sitter WebAssembly parser. The reviewed network behavior supports the installer and hook features; no credential theft, unrelated collector, or unrequested account action was identified.
Evidence
package.jsondist/index.jsdist/scanner/service.jsdist/runtime/signers.jsdist/install/journey.js
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a local installer and helper, has no lifecycle scripts, and exposes a CLI plus a library entry point.
- The library entry point re-exports modules without invoking an obvious startup routine.
- The scanner’s eval constructs functions from WebAssembly module strings; the wasm loader resolves web-tree-sitter.wasm relative to its module by default.
- Hook context data includes HMAC and repository fingerprint hashes rather than raw remote URLs.
- Install-session requests use the package’s api.mnemonik.dev service and send a bearer token with readiness data.
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.166.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.166.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.