create-zuplo-api@7.12.2
Create Zuplo API with one command
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe source shows a conditional credential exposure path: a saved Zuplo token is sent to an environment-configurable endpoint without a host restriction. The default endpoint and user-selected server-project setup are package-aligned, so this supports a warning rather than a block.
Decision evidence
public snapshot- The manifest exposes the CLI entrypoint and has no install lifecycle hook.
- The CLI reads a saved Zuplo access token from its local authentication file.
- The developer API destination can be replaced through an environment variable, and the CLI sends the saved token as a bearer credential to that destination.
- When server-project setup runs, it can use the saved token to look up accounts and project deployments.
- Server-project creation is called only when that feature is selected; the interactive prompt defaults to yes, while non-interactive setup skips it unless explicitly enabled.
- Agent configuration is written into the generated project only when agent choices are provided.
- The default credential recipient is Zuplo’s developer API, consistent with the CLI’s account and project setup.
- The agent setup is an explicit CLI choice and writes project-local configuration; no install hook performs it.
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.12.2.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.12.2 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.