@zaip-ai/cli@4.0.0
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package does not mutate agent config during npm install, but zaip init does rewrite the global Codex control file by default and installs a PreToolUse hook. That is an explicit user-command agent capability with a project-only opt-out, so it warrants a warning rather than a publish block.
Decision evidence
public snapshot- package.json exposes the zaip bin and has no preinstall, install, or postinstall script.
- zaip init turns on global Codex configuration unless the caller passes --project-only.
- reconcileGlobalCodexConfig writes CODEX_HOME or the home .codex/config.toml file.
- That writer installs a PreToolUse command hook into the global Codex config.
- installAgentsTemplate calls the global Codex writer after a template apply.
- The global write runs only from the explicit zaip init command, not from an npm lifecycle hook.
- --project-only skips reading or changing ~/.codex.
- The installed hook is a local command-safety policy and does not send credentials to a package endpoint.
Source & flagged code
8 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/services/stack-git.jsView on unpkg · L1Package hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.
templates/.agents/design/zaip-design.exeView on unpkgFindings
Affected versions and remediation
This report applies to @zaip-ai/cli@4.0.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@4.0.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.