@zaip-ai/cli@4.2.0
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is an explicit first-party installer that, by default, mutates the user's global Codex config when zaip init runs. That is a guarded agent-control capability with an opt-out, and it is not an unconsented install-hook hijack.
Decision evidence
public snapshot- The zaip init command, not an npm install hook, turns on global Codex config changes unless --project-only is set.
- After the project template is applied, reconcileGlobalCodexConfig writes CODEX_HOME or the user .codex/config.toml and installs ZAIP-owned hooks.
- package.json only publishes the zaip bin and build scripts; it has no preinstall, install, or postinstall hook.
- Global Codex mutation is skipped when the user passes --project-only.
- Hook replacement is limited to ZAIP-owned hook spans and cataloged legacy agent tables, with a backup file.
- Runtime dependencies are only commander and yaml; the package does not depend on itself.
Source & flagged code
9 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.2.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@4.2.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.