@byteplus-iga-pages/cli@1.1.16
A CLI tool for BytePlus IGA Pages
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package manifest, executable wrapper, and relevant bundled code are consistent with a BytePlus deployment CLI. The flagged behaviors were not confirmed: I found no concrete external credential theft or concealed remote execution, while the observed credential storage and gateway configuration writes support the package's stated purpose.
Decision evidence
public snapshot- The manifest identifies this as the BytePlus IGA Pages CLI and points to its bundled CLI entry point; it declares no lifecycle scripts.
- The executable wrapper only requires the CLI bundle.
- Telemetry is initialized with an explicit opt-out variable and filters sensitive parameter names.
- The AI Gateway integration command is described as creating or reusing a gateway and linking the project; related code writes gateway configuration to .env.local.
- Credential persistence writes to the CLI's auth file, consistent with login functionality.
- The static scanner flagged credential exfiltration and remote execution, but targeted searches found no OpenAI or Anthropic credential names, eval/new Function execution, or matching gateway endpoint in the bundle.
- The package includes an esbuild dependency with its ordinary platform-specific installer.
Source & flagged code
12 flaggedPackage source references child process execution.
dist/functions-runtime.jsView on unpkg · L11357Package source references dynamic require/import behavior.
bin/bp-iga.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @byteplus-iga-pages/cli@1.1.16.
See all versions of @byteplus-iga-pages/cli for other recorded verdicts.
- Review the evidence and your use of @byteplus-iga-pages/cli@1.1.16 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.