registry / @mnemonik/cli / 7.166.2
@mnemonik/cli@7.166.2
Mnemonik installer and local project helper
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install hooks or runtime dependencies, and the main flagged code paths fit the package’s parser and authenticated project-context functions. The available evidence does not establish an attack.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI or invokes scanner and runtime features.
Impact
No malicious impact identified from the inspected paths.
Mechanism
The scanner fetches parser content and compiles it as WebAssembly. The signer posts project context using a Bearer token; inspected code does not show credentials sent to an unrelated host.
AI rationale
The manifest has no install hooks or runtime dependencies, and the main flagged code paths fit the package’s parser and authenticated project-context functions. The available evidence does not establish an attack.
Network endpoints1
api.mnemonik.dev
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package is described as a Mnemonik installer and local project helper, with a CLI entry point and library exports.
- The manifest has no lifecycle scripts and no runtime dependencies.
- The scanner compiles fetched content as WebAssembly; the flagged dynamic evaluation appears in generated Emscripten glue for parser bindings.
- The runtime signer sends a Bearer-authenticated JSON request and binds project context, including a hashed repository fingerprint.
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.2.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.166.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.