@zuplo/cli@7.7.13
<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 2mo ago · by lpm-firewall-aiThis is a first-party Zuplo CLI with no npm lifecycle scripts; inspectable code matches deploy, lint, local runtime, and PostHog telemetry. A clean verdict is not grounded because a nested binary zip cannot be cited as text and large minified bundles exceeded complete static coverage.
Decision evidence
public snapshot- Bundled first-party minified files in @zuplo/core and @zuplo/runtime are too large and opaque for complete static review.
- A nested binary zip at node_modules/thread-stream/test/dir with spaces/test-package.zip cannot be read as text.
- User-invoked migrate and lint commands spawn git and a native lint binary.
- CLI telemetry hashes a machine identifier and sends events to PostHog.
- package.json has no scripts field and no preinstall, install, or postinstall hooks.
- zup.js only imports dist/cli.js; nothing runs automatically at npm install time.
- Inspectable CLI network defaults are Zuplo APIs, Auth0, and PostHog, not off-vendor steal endpoints.
- The zip is referenced only from a thread-stream yarn PnP test, not from CLI runtime.
- zeno.js env and Redis usage matches a local Zuplo worker runtime; CodeMirror bidi matches editor RTL handling.
Source & flagged code
20 flaggedPackage source references child process execution.
dist/source/migrate/dev-portal/handler.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @zuplo/cli@7.7.13.
See all versions of @zuplo/cli for other recorded verdicts.
- Review the evidence and your use of @zuplo/cli@7.7.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.