@zaip-ai/cli@2.6.0
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 install-hook abuse because it has no npm lifecycle trigger and requires an explicit CLI command. The command nevertheless creates a high-privilege AI-agent control surface and cloud-operation capability, so it warrants a warning.
Decision evidence
public snapshot- The explicit init command installs a project-local Codex configuration and three command hooks.
- The generated Codex configuration defaults to root filesystem write access and unrestricted network access.
- Init also reconciles the user's global Codex configuration unless --project-only is selected.
- A bundled cloud runner reads project token files and can perform Cloudflare, Hostinger, Terraform, and SSH operations.
- package.json has no preinstall, install, or postinstall lifecycle hook and no self-dependency.
- The control-surface changes require the user to run the zaip init command.
- The cloud runner limits credential files to the project and validates a contract before its operations.
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 · L1This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/services/stack-git.jsView on unpkgFindings
Affected versions and remediation
This report applies to @zaip-ai/cli@2.6.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@2.6.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.