@mnemonik/cli@7.167.0
Mnemonik installer and local project helper
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the flagged eval sites are WebAssembly runtime glue rather than evidence of remote response execution. The credential path references are part of scanner exclusions, and no malicious behavior was established in the reviewed source.
Decision evidence
public snapshot- The manifest has no lifecycle scripts, so installation does not automatically run package hooks.
- The flagged eval is part of Tree-sitter WebAssembly glue that builds functions from the module’s embedded strings.
- Scanner path filters include credential locations such as .npmrc and exclude protected paths from candidate selections.
- The bootstrap validates the installed package path and lockfile before proceeding.
- The package exposes a CLI that performs installation and project setup when explicitly invoked.
- The source includes network and process APIs for scanner, update, and hook functionality, but the reviewed excerpts do not show an attack chain.
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.167.0.
See all versions of @mnemonik/cli for other recorded verdicts.
- Review the evidence and your use of @mnemonik/cli@7.167.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.