@mdevs/mai-cli
The mAI agent, directly in your terminal!
This report shows the evidence for @mdevs/mai-cli@1.0.20. 3 of 8 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package performs automatic postinstall registration of an external Chrome MCP bridge and permission changes. That is a concrete unconsented AI-agent control-surface mutation.
Decision evidence
public snapshot- The npm postinstall hook automatically launches Chrome MCP setup.
- That setup resolves an external bridge and runs its register command for Chrome.
- It also runs a permission-changing command without an explicit user action.
- The separate postinstall downloader only targets a ripgrep release URL and writes inside the package.
Source & flagged code
26 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/chunks/exit-BbAyh7iz.jsFindings
Affected versions and remediation
This report applies to @mdevs/mai-cli@1.0.20.
The versions list below shows the verdict for each recorded version.
- Avoid installing @mdevs/mai-cli@1.0.20. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.