registry / @mnemonik/cli / 7.167.4
@mnemonik/cli@7.167.4
Mnemonik installer and local project helper
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install hooks, and the flagged dynamic evaluation belongs to the local WebAssembly scanner. Network activity appears tied to user-invoked setup and the package’s own API; the reviewed hook-context data uses project hashes rather than credentials.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when a user invokes the command; setup reporting occurs within that flow.
Impact
No credential theft, unrelated code execution, or unrequested account action was identified.
Mechanism
The scanner uses generated WebAssembly glue, and setup requests go to the Mnemonik API. The reviewed hook-context payload uses hashes for project context.
AI rationale
The manifest has no install hooks, and the flagged dynamic evaluation belongs to the local WebAssembly scanner. Network activity appears tied to user-invoked setup and the package’s own API; the reviewed hook-context data uses project hashes rather than credentials.
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 has no lifecycle scripts or runtime dependencies.
- The CLI entry point starts its bootstrap flow when invoked with command-line arguments.
- The flagged eval builds functions from WebAssembly module contents; the scanner’s Node path loads the Wasm file locally.
- The setup flow contacts the package’s own API for install-session and readiness handling.
- The hook-context payload contains a project-root HMAC and repository fingerprint, rather than credential values.
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.167.4.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.167.4 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.