@zaip-ai/cli@6.0.1
⚠ Under reviewCLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe inspected manifest and source do not establish malicious behavior, and the scanner findings alone are not proof. The flagged binary remains unresolved, so a clean verdict is not supported.
Decision evidence
public snapshot- The manifest exposes a CLI and defines build and packaging scripts, but no install lifecycle hook.
- The Codex hook references occur in test and fixture code that writes sample hooks into temporary directories.
- The doctor service checks for design and runtime files; the inspected source does not show it executing the flagged design binary.
- The flagged binary could not be verified as source, so its behavior remains unresolved.
- The manifest has no preinstall, install, or postinstall script.
- The inspected Git setup code uses a package-aligned Git for Windows release and verifies its SHA-256 before use.
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.0.1.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@6.0.1 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.