create-zuplo-api@7.8.18
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiAgent configuration is an explicit, user-gated CLI feature of this scaffolder, not an npm install hook or hidden exfiltration path. It still enables project MCP servers and installs unpinned first-party agent skills, so it is a guarded agent capability rather than a clean no-op.
Decision evidence
public snapshot- The create-zuplo-api bin prompts which AI agents to configure, or accepts --agents, and only then writes agent files into the new project.
- Claude setup writes .claude/settings.json that enables zuplo-tools plugins and enableAllProjectMcpServers, plus a project .mcp.json for the Zuplo docs MCP.
- When non-Claude agents are selected, the CLI downloads an unpinned zuplo/tools main tarball and copies SKILL.md files into that agent's skill directory.
- package.json has no preinstall, install, or postinstall hook; agent writes run only from the explicit CLI.
- Non-interactive runs set agents to an empty list and skip setup.
- The MCP URL is the vendor docs endpoint https://dev.zuplo.com/mcp/docs, and writes stay inside the newly created project directory.
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.18.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.8.18 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.