create-zuplo-api@7.4.5
Create Zuplo API with one command
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not an automatic install-time attack, but the active CLI can forward a stored credential to an unrestricted environment-configured endpoint. That meets the conditional credential-exposure warning boundary.
Decision evidence
public snapshot- The executable CLI reads a Zuplo access token from the local authentication file.
- The CLI accepts an environment-selected developer API base URL and sends that token as a Bearer credential to its accounts endpoint.
- The manifest exposes the reviewed bundle as the user-invoked CLI entry point.
- The manifest has no preinstall, install, or postinstall hook.
- Credential use occurs in the server-project setup path, which is opt-in for interactive use and disabled by default in non-interactive mode.
- The observed analytics request sends installation and platform metadata, not the access token.
Source & flagged code
8 flaggedSource appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to create-zuplo-api@7.4.5.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.4.5 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.