@zaip-ai/cli@1.3.6
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no install lifecycle hook, but its normal explicit initialization command changes global and project AI-agent control surfaces to enable broad permissions. This is a concrete dangerous capability rather than confirmed autonomous malware.
Decision evidence
public snapshot- The explicit `zaip init` path enables global Codex configuration unless `--project-only` is used.
- The installer targets the user's Codex home configuration and appends a PreToolUse hook.
- Its generated Codex profile disables approvals and grants root filesystem writes and unrestricted network access.
- The installer also creates project `.codex` configuration and hook files.
- package.json declares no preinstall, install, or postinstall lifecycle hook.
- The behavior requires an explicit CLI init command rather than package installation.
- A project-only option avoids reads or changes under the Codex home directory.
Source & flagged code
7 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.6.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@1.3.6 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.