create-zuplo-api@7.8.22
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected source supports a warning for conditional credential forwarding and guarded agent configuration. Explicit CLI activation, package-aligned defaults, and absent install hooks do not support a malicious verdict.
Decision evidence
public snapshot- The package exposes dist/index.js as its CLI and declares no install lifecycle hooks or runtime self-dependency.
- Selected agent setup writes project-local instructions, MCP configuration, and Claude settings enabling Zuplo marketplace plugins and all project MCP servers.
- Agent selection requires a CLI flag or interactive selection; non-interactive execution defaults to no agents, and agent choices are not saved.
- Server-project setup reads an existing Zuplo access token from its authentication file.
- ZUPLO_DEVELOPER_API_ENDPOINT selects the API destination without an enforced destination restriction.
- The active server-project setup forwards the stored token as bearer authentication when fetching accounts.
- The default authentication destination is the package-aligned https://dev.zuplo.com.
- Agent configuration occurs during explicit project creation, with no npm install hook mutation.
- No concrete covert exfiltration or malware intent 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.8.22.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.8.22 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.