@zaip-ai/cli@5.8.0
⚠ Under reviewCLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 25d ago · by lpm-firewall-aiStatic source inspection found no confirmed malicious behavior, but the required design executable is binary and its behavior could not be verified. The unresolved binary prevents a clean classification, so manual review is appropriate.
Decision evidence
public snapshot- The manifest exposes a CLI and package exports, with no preinstall, install, or postinstall hook.
- Doctor checks for the design executable in a project and reads its bytes as part of package-aligned project diagnostics.
- The package contains project-scoped Codex hook setup and activation code; the inspected activation code records local diagnostic metadata.
- The supplied design executable is a verified binary that cannot be inspected as UTF-8 source, so its behavior remains unresolved.
- The inspected test and fixture excerpts show Codex hook files being written into temporary test projects, not evidence of an npm install hook.
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@5.8.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@5.8.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.