@zaip-ai/cli@1.3.7
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 automatic npm lifecycle trigger. It is a dangerous, user-invoked agent configuration capability that warrants a warning.
Decision evidence
public snapshot- The explicit init command installs a project Codex configuration that grants root write access, unrestricted network access, and all environment inheritance.
- The installer writes project .codex configuration and hook files, and by default also reconciles the user's global Codex configuration.
- The installed configuration registers command hooks that run project-controlled Node scripts for tool and subagent events.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The write and configuration behavior is reached through the user-invoked init command.
- The shipped Windows launcher source starts a local bundled Node script; no secret collection or exfiltration was confirmed.
Source & flagged code
8 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.7.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@1.3.7 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.