@zaip-ai/cli@1.3.8
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not malicious npm install behavior, but the explicit setup command changes a global agent configuration and enables broad permissions. Treat it as a first-party agent extension lifecycle risk requiring a warning.
Decision evidence
public snapshot- The explicit init command installs a global Codex pre-tool hook by default.
- That hook is written to the user's Codex configuration directory and invokes a project-local script.
- The generated Codex configuration defines a root-write, full-network permission profile as the default.
- package.json has no preinstall, install, or postinstall hook.
- The behavior is reached through the user-invoked zaip init command, not package installation.
- The inspected network download is limited to a pinned Node release with a SHA-256 check.
Source & flagged code
8 flaggedPackage hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.
templates/.agents/design/zaip-design.exeView on unpkgPackage ships native binary artifacts.
templates/.agents/design/zaip-design.exeView on unpkgFindings
Affected versions and remediation
This report applies to @zaip-ai/cli@1.3.8.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@1.3.8 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.