@zaip-ai/cli@3.6.0
CLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is not malicious install-hook behavior because the package has no automatic npm installation hook and the change is reached through `zaip init`. It warrants a warning because the default explicit command modifies global Codex configuration and installs agent hooks.
Decision evidence
public snapshot- The package exposes an explicit `zaip init` command rather than an npm install lifecycle hook.
- Running `init` enables global Codex configuration unless the user selects `--project-only`.
- The global configuration routine targets the user's Codex config file and installs a command safety hook.
- The project template writes Codex configuration and hook files into the selected repository.
- No package lifecycle install, preinstall, or postinstall hook was found in package metadata.
- The global mutation is reached through the user-invoked `init` command, and `--project-only` avoids it.
- No credential collection, exfiltration sink, or covert remote payload execution was identified in the inspected path.
Source & flagged code
9 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@3.6.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@3.6.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.