create-zuplo-api@7.9.6
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection establishes conditional credential exposure and explicit agent configuration capabilities, warranting a warning. The source does not support the scanner's malicious-package block.
Decision evidence
public snapshot- The manifest has no npm install lifecycle hooks or runtime self-dependency.
- The CLI locates an existing Zuplo authentication file and reads its access token.
- The developer API endpoint accepts an environment override without destination restrictions; account requests send the saved token as bearer authentication.
- Server-project setup activates token-backed requests through the explicit CLI setup flow.
- Selected agent setup writes project-local instructions, skills and MCP configuration; Claude settings enable Zuplo plugins and all project MCP servers.
- Agent configuration requires a CLI selection or flag; noninteractive execution defaults to no agents.
- The default credential recipient is the intended Zuplo service.
- No covert credential export or malicious install-time behavior was established.
- Project creation, dependency installation and Git initialization match the scaffolding command's purpose.
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.6.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.9.6 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.