create-zuplo-api@7.8.21
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected source supports a warning for conditional credential forwarding and guarded agent configuration capability. It does not establish malware or an automatic install attack.
Decision evidence
public snapshot- The CLI reads an existing Zuplo access token from its saved authentication file.
- The developer API endpoint accepts an environment override without destination validation.
- Account lookup forwards the saved token as a bearer credential to that endpoint.
- Server-project setup activates this lookup after a CLI flag or interactive consent.
- Selected agent setup writes project instructions, MCP configuration, and Claude settings.
- No npm install lifecycle hooks or runtime self-dependency are declared.
- The default credential recipient is Zuplo's developer API; no covert unrelated recipient was identified.
- Agent setup requires explicit selection and is skipped by default in noninteractive mode; agent choices are not saved preferences.
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.21.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.8.21 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.