@zaip-ai/cli@4.3.0
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package exposes a concrete high-authority agent setup through its explicit init command. The behavior warrants a warning for agent capability abuse, but static inspection found no automatic install-time mutation or confirmed exfiltration.
Decision evidence
public snapshot- The explicit init command installs project agent adapters.
- Generated Codex configuration defaults to unrestricted permissions.
- The generated profile allows root writes and unrestricted network access.
- The package metadata has no npm install lifecycle hook.
- The configuration change is triggered by an explicit CLI init action, not package installation.
- Global Codex reconciliation removes its own legacy entries and does not install a global fallback.
Source & flagged code
9 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@4.3.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@4.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.