@mnemonik/cli@7.170.0
Mnemonik installer and local project helper
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest has no install hooks or runtime dependencies, and the reviewed eval, network, and helper execution paths have package-related purposes. The observed context reporting sends hashes rather than raw paths or Git remotes.
Decision evidence
public snapshot- The manifest has no lifecycle scripts or runtime dependencies.
- The scanner's eval calls build JavaScript functions from code embedded in the WebAssembly module; the module defaults to a local web-tree-sitter.wasm path.
- Install-session reporting requires an available CLI bearer and sends to the Mnemonik API.
- Hook context binding posts a device-root HMAC and repository fingerprint hash to a supplied server.
- Bundled scanner and diagnostics files contain eval calls.
- The package can make network requests and run local helper commands.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/diagnostics.jsView on unpkg · L923Package source references dynamic require/import behavior.
dist/diagnostics.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @mnemonik/cli@7.170.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.170.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.