@zuplo/cli@7.9.18
⚠ 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 27d ago · by lpm-firewall-aiThe manifest and inspected source excerpts do not confirm malicious behavior, and the runtime log transfer appears to be a configured logging feature. Required finding paths remain unresolved, including a binary archive that cannot be cited as source, so the evidence is insufficient to mark the package clean or establish an attack.
Decision evidence
public snapshot- package.json identifies the Zuplo CLI and exposes zup.js, with no lifecycle scripts in the inspected manifest.
- The runtime log sender requires configured remote log URL, logging ID, and token before sending logs.
- The core bundle reads process environment and the local .env.zuplo configuration for runtime setup.
- The required archive path is binary and cannot be verified using the required source citation method, so the flagged artifact remains unresolved.
- The inspected runtime transfer is gated by configured logging credentials and sends runtime logs.
- The inspected test, migration, analytics, machine-id, and editor excerpts do not establish the flagged attack behavior.
Source & flagged code
21 flaggedPackage source references child process execution.
dist/source/ai-gateway/package.test.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.9.18.
See all versions of @zuplo/cli for other recorded verdicts.
- Review the evidence and your use of @zuplo/cli@7.9.18 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.