create-zuplo-api@7.9.5
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource supports a warning for conditional credential exposure and guarded agent configuration capability, rather than the scanner's malicious classification. No concrete attack behavior warrants publication blocking.
Decision evidence
public snapshot- The manifest has no npm install lifecycle hooks; setup runs through the CLI.
- The developer API endpoint accepts ZUPLO_DEVELOPER_API_ENDPOINT without a destination allowlist.
- The CLI reads an existing Zuplo access token and sends it as bearer authentication to the selected endpoint.
- Server-project setup calls the saved-token account lookup when no account is selected.
- Agent selection is prompted or supplied explicitly; noninteractive mode defaults to no agents.
- Selected agent setup writes project instructions and MCP configuration and enables Zuplo Claude plugins through a GitHub marketplace.
- The default authenticated destination is https://dev.zuplo.com, consistent with Zuplo project setup.
- No concrete covert exfiltration or malicious install behavior was established.
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.5.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.9.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.