create-zuplo-api@7.11.6
Create Zuplo API with one command
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe scanner’s execution and credential indicators are consistent with bundled dependencies and normal CLI operations; inspected source shows no install-time credential transfer. The optional agent setup changes how selected project agents load plugins and MCP servers, so it warrants a warning under the agent integration policy.
Decision evidence
public snapshot- The manifest points the CLI command to dist/index.js and declares no npm install lifecycle hook.
- Agent selections map to project paths such as .claude/skills and AGENTS.md.
- The CLI asks which agents to configure and defaults to no agents in noninteractive runs.
- For selected agents, it writes project-local agent and MCP files; Claude settings enable Zuplo plugins and all project MCP servers.
- Project creation calls agent setup only when the selected agent list is nonempty.
- The setup uses Zuplo’s documentation MCP service and downloads skills from Zuplo’s GitHub archive.
- Agent configuration requires running the CLI and selecting agents; it is not triggered by npm installation.
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.11.6.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.11.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.