@zaip-ai/cli@5.2.0
⚠ Under reviewCLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe inspected manifest has no install lifecycle hook, and the doctor code treats design files as required files rather than executing them. The bundled design executable and large runtime bundle leave material behavior unresolved, so the source does not support a clean verdict.
Decision evidence
public snapshot- package.json defines build and prepack scripts but no npm lifecycle hook; the CLI starts through the `zaip` executable.
- The doctor service reads and checks project files, and lists design documents and web pages as required files.
- On Windows, the Git installer checks the downloaded archive against a SHA-256 digest before extracting it.
- The package includes an unsupported executable artifact at `templates/.agents/design/zaip-design.exe`; its behavior remains unresolved.
- The inspected source does not establish that the doctor service executes the design artifact.
- The inspected Windows Git installer uses GitHub’s release API and validates the archive digest before extraction.
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.2.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@5.2.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.