@zuplo/cli@7.12.3
⚠ Under review<p align="center"> <a href="https://zuplo.com"> <img src="https://portal.zuplo.com/zuplo.svg" height="96"> <h3 align="center">Zuplo</h3> </a> </p> <p align="center">Zuplo's API Gateway helps small and large teams get APIs to production that ar
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe inspected credential flow targets the configured Zuplo developer API, and the usage telemetry has an opt-out. I cannot mark the package clean because required source paths remain unresolved, so the source evidence does not support a malicious verdict or a clean one.
Decision evidence
public snapshot- package.json defines the CLI entry point and shows no lifecycle scripts.
- Project information commands send the supplied token to the configured Zuplo developer API; its default is dev.zuplo.com.
- The CLI sends usage events to its configured PostHog collector and supports the ZUPLO_DO_NOT_TRACK opt-out.
- Telemetry can include a hashed machine identifier and account, project, and CI values.
- Required clean-review coverage includes many uninspected source paths and a binary archive that cannot be cited as UTF-8 source.
- The inspected credential requests target the Zuplo developer API, not an unrelated recipient.
- Telemetry is tied to CLI command invocation and has a tracking opt-out; the inspected files do not establish credential collection or an attack.
Source & flagged code
20 flaggedPackage source references child process execution.
dist/source/ai-gateway/files.jsView on unpkg · L1Package source references shell execution.
dist/source/migrate/dev-portal/handler.jsView on unpkg · L20Findings
Affected versions and remediation
This report applies to @zuplo/cli@7.12.3.
See all versions of @zuplo/cli for other recorded verdicts.
- Review the evidence and your use of @zuplo/cli@7.12.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.