registry / @mnemonik/cli / 7.170.3
@mnemonik/cli@7.170.3
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package has no lifecycle scripts, and the flagged dynamic evaluation supports the bundled WebAssembly scanner. The credential-related path matches protect local credential files, while the hook-context sender has no default caller in this package.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI bootstrap runs when a user invokes the mnemonik command. No install hook or suspicious import-time action was found.
Impact
No unsolicited credential collection, unrelated code execution, or account action was identified.
Mechanism
The reviewed dynamic evaluation builds scanner parser functions from WebAssembly contents. A hook helper can post hashed project context to its supplied server, but no default caller was found.
AI rationale
The package has no lifecycle scripts, and the flagged dynamic evaluation supports the bundled WebAssembly scanner. The credential-related path matches protect local credential files, while the hook-context sender has no default caller in this package.
Network endpoints4
api.mnemonik.devauth.mnemonik.aigithub.comregistry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines no lifecycle scripts or runtime dependencies.
- The CLI bootstrap runs after command-line invocation; the package entry exports modules without starting the CLI.
- The scanner loads web-tree-sitter.wasm relative to its own module; its eval calls construct parser functions from WebAssembly data.
- The scanner identifies credential-bearing local paths such as .npmrc as protected paths.
- The hook-context helper sends project context as HMAC and fingerprint hashes, rather than raw repository URLs or credential contents.
Evidence against
- The hook-context helper can POST host/session identifiers and project hashes using a bearer token, but no caller or default trigger for that helper was found in this package.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStrings
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.170.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.170.3 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.