@zaip-ai/cli@2.2.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 a user-invoked agent-extension and cloud-management CLI with real sensitive capabilities. The absence of install hooks and the contract and target checks make malicious intent unproven, but the global control-surface mutation and credential-backed cloud actions warrant a warning.
Decision evidence
public snapshot- The user-invoked init command enables a global Codex configuration update unless project-only mode is selected.
- The installer writes a Codex hook into the user's Codex configuration.
- The bundled cloud runner reads Cloudflare and Hostinger API tokens from project environment files and can change approved DNS records.
- The manifest has no preinstall, install, or postinstall hook.
- The risky behavior follows an explicit CLI init or cloud-runner command rather than package installation or import.
- Cloud operations enforce an approved contract, exact operation names, and account and zone matching.
- No source path inspected sends harvested credentials or arbitrary local files to an unrelated 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@2.2.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@2.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.