create-zuplo-api@7.10.0
Create Zuplo API with one command
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe package has no npm install lifecycle hook, but its explicit CLI agent setup writes project-level configuration enabling plugins and MCP servers. Classify this as a guarded agent capability risk and warn rather than block.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI and lists development/build scripts, with no preinstall, install, or postinstall hook.
- Agent configuration requires an explicit --agents selection or an interactive choice; CI and --yes leave the agent list empty.
- Selected setup writes project-level agent files. Claude settings enable two Zuplo plugins, register the Zuplo tools marketplace, and enable all project MCP servers.
- The configured Zuplo MCP server is https://dev.zuplo.com/mcp/docs.
- The agent setup is guarded by user selection and is part of explicit project creation, not npm installation.
- The observed agent integration points to Zuplo-controlled plugins and an MCP server; source inspection did not establish credential theft or another active attack.
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.10.0.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.10.0 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.