@zaip-ai/cli@3.7.0
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe source establishes an explicit-user-command global AI-agent configuration mutation, but not an automatic or covert attack. The package has no install lifecycle hook and the inspected paths do not establish exfiltration or destructive behavior.
Decision evidence
public snapshot- The CLI's explicit init command installs a global Codex PreToolUse hook unless the user selects project-only mode.
- The global-config routine reads and rewrites the user's Codex config file to add the package hook.
- This occurs only after the user invokes the init workflow; package installation has no lifecycle hook.
- package.json defines no preinstall, install, or postinstall script.
- No credential collection, exfiltration sink, or automatic package-time execution was found in the inspected entrypoints.
- The bundled Windows executable is a template asset and no inspected package entrypoint automatically launches it.
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@3.7.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@3.7.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.