create-zuplo-api@7.9.4
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource supports a warning for conditional forwarding of an existing service credential to an unrestricted configured endpoint, plus guarded agent configuration capability. No automatic install attack or concrete malware behavior was identified.
Decision evidence
public snapshot- The CLI reads an existing Zuplo access token from the user's Zuplo authentication file.
- The developer API destination accepts ZUPLO_DEVELOPER_API_ENDPOINT without an allowlist, and account requests send the saved token as bearer authentication.
- Server-project creation activates token discovery and account requests; this follows a CLI flag or interactive setup choice.
- Agent setup requires an explicit selection and defaults to no agents in non-interactive mode.
- Selected agent setup writes project instructions, MCP configuration and Claude settings enabling Zuplo marketplace plugins.
- The manifest has no install lifecycle hooks or runtime self-dependency.
- The default authentication destination is Zuplo's developer API; no covert unrelated recipient was identified.
- Project installation commands and analytics match the scaffolding workflow; analytics sends selected options and runtime metadata.
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.9.4.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.9.4 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.