@iga-pages/cli@1.1.3
A CLI tool for IGA Pages
AI Security Review
scanned 3mo ago · by lpm-firewall-aiInspection found no lifecycle execution, secret harvesting, remote-code execution, or unconsented persistence. Scanner hits are explained by bundled dependencies and normal Volcengine CLI functionality; telemetry is sanitized and package-aligned.
Decision evidence
public snapshot- dist/index.js sends CLI telemetry to mcs.zijieapi.com or sgali-mcs.byteoversea.com.
- dist/index.js invokes project build/dev commands only through explicit CLI commands.
- package.json has no preinstall, install, or postinstall hook.
- bin/iga.js only loads dist/index.js; commands are parsed from user argv.
- Telemetry excludes accessKey, secretKey, and value parameters.
- OAuth, deployment, env pull, and credential writes are explicit user-invoked CLI functions.
- Function constructor is bundled protobufjs code, not a package payload path.
Source & flagged code
11 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L34Source executes local commands and sends command output to an external endpoint.
Findings
Affected versions and remediation
This report applies to @iga-pages/cli@1.1.3.
See all versions of @iga-pages/cli for other recorded verdicts.
- Review the evidence and your use of @iga-pages/cli@1.1.3 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.