create-zuplo-api@7.8.20
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection supports a warning for conditional credential forwarding to an unrestricted configured endpoint and guarded agent integration. Explicit activation and package-aligned defaults do not establish malware intent or justify a publication block.
Decision evidence
public snapshot- package.json declares no automatic install lifecycle hooks or runtime self-dependency.
- Agent setup requires CLI selection or --agents; noninteractive defaults skip it.
- Selected agents receive project-local configuration; Claude settings enable Zuplo marketplace plugins and all project MCP servers.
- Server-project setup reads an existing Zuplo access token from the user's authentication file.
- ZUPLO_DEVELOPER_API_ENDPOINT can replace the intended service endpoint without destination validation; account requests send the stored bearer token there.
- The active server-project setup calls token reading and account fetching when no account is supplied.
- The default API recipient is https://dev.zuplo.com, and server-project setup requires a CLI flag or affirmative prompt.
- Agent setup is explicitly selected and confined to the generated project; no covert install-time mutation was identified.
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.8.20.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.8.20 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.