@mnemonik/cli@7.140.2
⚠ Under reviewMnemonik installer and local project helper
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no npm lifecycle hook, and the inspected credential and dynamic-evaluation excerpts do not prove an attack. The runtime update and installation behavior was not fully traced, so the available source does not support a confident clean or malicious verdict.
Decision evidence
public snapshot- package.json has no npm lifecycle scripts.
- The CLI bootstraps only from a verified installed package and routes execution through its runtime store.
- Credential readers reject declarations with caller-supplied authorization headers or tokens.
- Generated WebAssembly glue uses eval to construct functions from module-provided data.
- The manifest defines the CLI entrypoints and no install hook.
- The inspected auth code does not establish an unrestricted credential transfer.
- The eval match is in WebAssembly runtime glue; the inspected excerpt does not show attacker-controlled input reaching it.
Source & flagged code
9 flaggedPackage source references child process execution.
dist/diagnostics.jsView on unpkg · L919Package source references dynamic require/import behavior.
dist/diagnostics.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @mnemonik/cli@7.140.2.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.140.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.