@zaip-ai/cli@5.3.0
⚠ Under reviewCLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe inspected doctor code only checks for files, and the companion launcher source describes starting a workspace-local design runtime. The packaged launcher is identified as a binary whose actual behavior could not be verified, so a clean verdict is not supported.
Decision evidence
public snapshot- The doctor checks a fixed list of design files; its helper reads file contents rather than executing the launcher.
- The template manifest includes the Windows launcher as a binary file with a recorded hash.
- The companion C# source starts Node with the workspace-local design startup script.
- Package documentation describes a user double-click workflow that opens the local Design System.
- The launcher’s actual binary behavior could not be verified from the available source inspection.
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.3.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@5.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.