@mnemonik/cli@7.164.3
Mnemonik installer and local project helper
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package has no lifecycle scripts, and the flagged remote-code and eval patterns are explained by WebAssembly parser loading. The reviewed network request sends installer readiness to the package's API as part of the CLI workflow.
Decision evidence
public snapshot- The manifest has no lifecycle scripts or runtime dependencies.
- The scanner compiles fetched input as WebAssembly for its parser loader; the flagged eval is part of Emscripten glue that reads functions from the WebAssembly module.
- The install workflow contacts api.mnemonik.dev to retrieve or complete an install session using a CLI bearer token and readiness data.
- The scanner contains eval and network access, but the reviewed code uses the response as WebAssembly input rather than evaluating it as ordinary JavaScript.
- The CLI bootstrap runs when the executable is invoked; no install-time hook is configured.
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.164.3.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.164.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.