create-zuplo-api@7.8.25
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe unrestricted endpoint override can forward existing service credentials, which meets the conditional credential-exposure warning rule. Agent integration is user-selected rather than an unconsented npm install hook, so publication blocking is unsupported.
Decision evidence
public snapshot- package.json routes the CLI to dist/index.js and defines no registry install lifecycle hooks.
- The developer API endpoint accepts ZUPLO_DEVELOPER_API_ENDPOINT without destination validation.
- The CLI reads an existing access token from the Zuplo auth.json file and sends it as a bearer credential to the selected endpoint.
- Server-project setup calls the token reader and account request after activation through the CLI flag or interactive prompt.
- Agent setup requires CLI selection and writes project-local instructions and MCP settings; noninteractive defaults select no agents.
- Claude setup enables Zuplo marketplace plugins and all project MCP servers, creating a guarded extension capability.
- The default credential recipient is https://dev.zuplo.com, aligned with Zuplo authentication.
- No covert credential export or malicious install-time mutation was identified; server-project and agent setup are user-invoked.
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.25.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.8.25 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.