create-zuplo-api@7.4.4
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe active credential flow forwards a saved service token to an unrestricted environment-configured endpoint, meeting the conditional credential-exposure warning policy. Guarded agent plugin setup provides an additional warning basis, while no block-eligible attack was identified.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI entrypoint.
- Server-project setup reads an existing Zuplo access token from the user's saved authentication file.
- ZUPLO_DEVELOPER_API_ENDPOINT overrides the API destination without a destination allowlist.
- Account requests send the saved token in the Authorization header.
- The active CLI calls token-based account discovery when server-project setup is enabled.
- Agent selection is prompted interactively and defaults to none noninteractively; selected Claude setup enables Zuplo marketplace plugins and project MCP servers.
- 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 configuration is scoped to the generated project and requires a selection or explicit CLI flag.
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.4.4.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.4.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.