@zaip-ai/cli@1.3.0
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis package is not conclusively malicious, but explicit CLI setup mutates global Codex configuration and ships an unauditable executable payload. No install-time execution or confirmed data exfiltration was found.
Decision evidence
public snapshot- The manifest exposes a user-invoked zaip CLI and has no install lifecycle hook.
- The init command enables global Codex configuration changes unless --project-only is selected.
- Global reconciliation writes a ZAIP PreToolUse hook into the user's Codex configuration.
- The template declares and distributes an opaque Windows executable; its PE payload has not been source-audited.
- No package lifecycle script runs on npm installation.
- The doctor service only reads project files and checks required-file hashes; it does not execute the design executable.
Source & flagged code
10 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.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@1.3.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.