registry / @zaip-ai/cli / 6.0.0
@zaip-ai/cli@6.0.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 manifest has no install lifecycle hook, and the agent-integration hints point to test code or project-level hook paths. The required binary remains unresolved, so the package cannot be cleared from source inspection alone.
Static reason
One or more suspicious static signals were detected.
Trigger
Unknown; the executable's behavior could not be inspected as source.
Impact
Unknown because the executable behavior is unresolved.
Mechanism
The available source shows doctor checks for required project files, but does not establish execution of the flagged design executable.
AI rationale
The inspected manifest has no install lifecycle hook, and the agent-integration hints point to test code or project-level hook paths. The required binary remains unresolved, so the package cannot be cleared from source inspection alone.
Evidence
templates/.agents/design/zaip-design.exe
Decision evidence
public snapshotAI called this Manual Review at 77.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json lists build and prepack scripts but no install lifecycle hook.
- The inspected agent-integration locations are in test fixtures, tests, or declarations of project-level Codex hook paths.
- doctorProject checks for dashboard and runtime files; the inspected code does not establish execution of the flagged design executable.
- The required design executable is non-UTF-8 and its behavior could not be established from source inspection.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
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.0.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@6.0.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.