@zuplo/cli
<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
This report shows the evidence for @zuplo/cli@7.13.13. 0 of 109 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe source shows automatic runtime analytics to PostHog with command, version and Zuplo account or user identifiers, plus a ZUPLO_DO_NOT_TRACK opt-out. The inspected package does not provide a user-facing disclosure, so this is a warning-level telemetry concern rather than credential exfiltration.
Decision evidence
public snapshot- The CLI invokes its analytics capture middleware during command dispatch.
- The invocation event includes the CLI version and parsed command; analytics also sends account/project context and a user or machine identifier to PostHog.
- The stored auth token is decoded locally for its subject identifier; the code does not send the token itself.
- Analytics can be disabled with ZUPLO_DO_NOT_TRACK.
- The observed analytics fields are usage metadata and Zuplo account identifiers, not credentials or project file contents.
- The package’s CLI behavior and Zuplo service calls are consistent with its stated purpose.
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.13.13.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @zuplo/cli@7.13.13 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.