create-zuplo-api@7.4.3
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 extension setup, without proving malware intent. These behaviors are user-invoked rather than npm install hooks, so publication blocking is unwarranted.
Decision evidence
public snapshot- package.json selects dist/index.js as the CLI and has no install lifecycle hooks or runtime self-dependency.
- Agent setup requires a CLI selection or flag; non-interactive defaults skip it. It writes project agent instructions and configuration.
- Claude configuration enables Zuplo marketplace plugins and all project MCP servers; other selected agents receive downloaded Zuplo skills.
- Server-project setup reads an existing Zuplo access token and sends it as bearer authentication to an environment-configurable endpoint without destination validation.
- The default API recipient is https://dev.zuplo.com, and server-project setup requires a prompt selection or explicit CLI option.
- Agent changes are confined to the requested project. No covert install-time agent mutation or confirmed malicious intent was identified.
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.3.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.4.3 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.