@zaip-ai/cli@5.9.0
⚠ Under reviewCLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe manifest has no npm install lifecycle hook, and the inspected source does not establish malicious behavior. The required bundled executable remains unresolved, so the evidence does not support a clean verdict.
Decision evidence
public snapshot- package.json declares a CLI entry point and no preinstall, install, or postinstall hook.
- doctor.js checks for required design files; it does not load the flagged executable.
- The Windows Git setup uses a verified Git release in the project’s .local directory.
- The inspected agent configuration locations are test fixtures or list hook paths; they do not establish an attack.
- The required bundled executable could not be reviewed as UTF-8 source, so its behavior remains unresolved.
- The manifest contains no npm install lifecycle hook.
- The inspected doctor code checks file presence, and the Git installer verifies the downloaded archive 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@5.9.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@5.9.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.