@zaip-ai/cli@6.3.0
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe package has no npm lifecycle hooks, while its agent configuration behavior is reachable through explicit CLI initialization and includes project-hook verification. This warrants a warning for agent configuration capability, but the inspected evidence does not establish malicious behavior.
Decision evidence
public snapshot- The manifest defines a CLI entry point and no install lifecycle hook.
- Running the explicit `zaip init` command can install project Codex hooks and update global Codex configuration unless `--project-only` is set.
- The global configuration update requires verified project hooks; it does not establish an unconsented install-time attack.
- The flagged executable is binary data, and the doctor source does not directly load it.
- The agent setup is activated through an explicit CLI command, rather than an npm install hook.
- No confirmed credential theft, unrelated network exfiltration, or malicious payload execution was established.
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@6.3.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@6.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.