registry / @zaip-ai/cli / 6.2.0
@zaip-ai/cli@6.2.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 inspected source does not establish malicious behavior, and the flagged doctor path checks for required files rather than loading the executable. Because a required shipped binary remains unreadable as source, the package's behavior is unresolved and warrants manual review.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI can be run explicitly; the inspected manifest has no npm install lifecycle hook.
Impact
The inspected source does not establish an attack impact; the opaque executable prevents a clean assessment.
Mechanism
The doctor service checks whether required project files exist. The design executable itself could not be inspected as source.
AI rationale
The inspected source does not establish malicious behavior, and the flagged doctor path checks for required files rather than loading the executable. Because a required shipped binary remains unreadable as source, the package's behavior is unresolved and warrants manual review.
Evidence
templates/.agents/design/zaip-design.exe
Decision evidence
public snapshotAI called this Manual Review at 83.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json defines a CLI entry point and build scripts, with no npm install lifecycle hook.
- The doctor service lists the design executable as a required file and checks for missing files; the inspected code does not show it loading that executable.
- The global Codex configuration module describes a repository-only hook policy that preserves unrelated global configuration.
- The required design executable is binary and could not be inspected as UTF-8 source, so its behavior remains unresolved.
Evidence against
- The inspected manifest contains no preinstall, install, or postinstall hook.
- The doctor and CLI entrypoint excerpts show file checks and command dispatch, not activation of the design executable.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggeddist/services/stack-git.jsView file
1import { execFile } from "node:child_process";
L2: import { createHash } from "node:crypto";
...
L5: import { promisify } from "node:util";
L6: import { inflateRawSync } from "node:zlib";
L7: import { assertSafeDestination } from "./transactional-files.js";
L8: const exec = promisify(execFile);
L9: const API = "https://api.github.com/repos/git-for-windows/git/releases/latest";
L10: const KNOWN_DIGESTS = {
...
L12: };
L13: export function resolveGitForWindowsRelease(value, arch = process.arch) {
L14: const release = value;
...
L34: try {
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/services/stack-git.jsView on unpkg · L1templates/.agents/design/zaip-design.exeView file
•path = templates/.agents/design/zaip-design.exe
kind = payload_in_excluded_dir
sizeBytes = 7680
magicHex = [redacted]
High
Payload In Excluded Dir
Package hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.
templates/.agents/design/zaip-design.exeView on unpkgFindings
1 Critical3 High7 Medium5 Low
CriticalTrigger Reachable Excluded Directory Payloaddist/services/doctor.js
HighSandbox Evasion Gated Capabilitydist/services/stack-git.js
HighPayload In Excluded Dirtemplates/.agents/design/zaip-design.exe
HighSemantic Analysis Limiteddist/services/codex-pre-tool-hook-template.test.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarytemplates/.agents/design/zaip-design.exe
MediumShips Build Helpertemplates/.agents/design/packages/windows-launcher/build-design-launcher.ps1
MediumOversized Source Filetemplates/.agents/runtime/bin/zaip.mjs
MediumOversized Cli Entrypointtemplates/.agents/runtime/bin/zaip.mjs
Affected versions and remediation
This report applies to @zaip-ai/cli@6.2.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@6.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.