registry / @mnemonik/cli / 7.145.0
@mnemonik/cli@7.145.0
Mnemonik installer and local project helper
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected bootstrap validates npm integrity and rejects dependencies with install lifecycle scripts. Scanner eval matches are generated WebAssembly glue, while the indicated agent locations describe ignore patterns rather than configuration writes.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the mnemonik command or invoking exported CLI APIs.
Impact
No confirmed unauthorized execution, credential transfer, or agent configuration change was established.
Mechanism
The bootstrap stages runtime files after validating package identity, lockfile integrity, dependency contents, and file digests; the flagged eval expressions construct callbacks from embedded WebAssembly module strings.
AI rationale
The manifest has no install lifecycle hook, and the inspected bootstrap validates npm integrity and rejects dependencies with install lifecycle scripts. Scanner eval matches are generated WebAssembly glue, while the indicated agent locations describe ignore patterns rather than configuration writes.
Evidence
dist/runtime/bootstrap.js
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 84.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines the CLI entrypoint and has no lifecycle scripts.
- The flagged eval locations are generated WebAssembly glue that builds callbacks from module strings; the matches do not establish remote code execution.
- The bootstrap checks npm package integrity, rejects dependency lifecycle scripts, and verifies the packaged runtime before launch.
- The inspected agent integration locations describe scanner ignore patterns; they do not show agent configuration mutation.
Evidence against
- The package has runtime network, filesystem, and process capabilities, but the inspected bootstrap constrains package contents and verifies their integrity before launch.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
9 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 · L9235245var func = `(${args}) => { ${body} };`;
L5246: ASM_CONSTS[start] = eval(func);
L5247: }
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
2 Critical6 High4 Medium4 Low
CriticalRemote Response Code Executiondist/runtime/selfUpdate.js
CriticalPrevious Version Dangerous Deltadist/runtime/bootstrap.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
Affected versions and remediation
This report applies to @mnemonik/cli@7.145.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.145.0 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.