registry / @mnemonik/cli / 7.171.1
@mnemonik/cli@7.171.1
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe critical scanner alert is consistent with embedded WebAssembly glue rather than execution of fetched response text. No install hooks or runtime dependencies are declared, and the reviewed installer requires explicit acceptance before applying changes.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap, installation, and readiness reporting run when a user invokes the command; the package has no install lifecycle scripts.
Impact
No malicious impact identified; the inspected reporting targets the package service as part of installation.
Mechanism
The reviewed dynamic evaluation is part of WebAssembly glue, runtime downloads are integrity-checked, and installation requires consent flags.
AI rationale
The critical scanner alert is consistent with embedded WebAssembly glue rather than execution of fetched response text. No install hooks or runtime dependencies are declared, and the reviewed installer requires explicit acceptance before applying changes.
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes an installer and local project helper, has no lifecycle scripts or runtime dependencies, and points to a CLI bin and library entry point.
- The CLI runs its bootstrap when invoked; the help path prints help instead.
- The scanner's eval constructs functions from symbols embedded in WebAssembly glue; the inspected Node path reads the Wasm input from a file, and no remote response is shown reaching eval.
- Downloaded runtime tarballs must use HTTPS and match the integrity value recorded for the package.
- Automatic installation requires explicit apply and acceptance flags, plus host and scan-root selections where applicable.
- The install flow reports readiness to api.mnemonik.dev using the CLI bearer token during the invoked installation flow.
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 · 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.171.1.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.171.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.