create-zuplo-api@7.8.1
Create Zuplo API with one command
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is an explicit user-run scaffolder with no install lifecycle hook. It still mutates first-party AI-agent control files and pulls remote skill markdown when the user selects agents, so the publish decision is a warning rather than a block.
Decision evidence
public snapshot- package.json exposes a user-run bin at dist/index.js and its scripts are only dev, build, build:public, and test, with no preinstall, install, or postinstall hook.
- Agent setup runs only when the user passes --agents or answers an interactive multiselect; a truthy T path assigns an empty agent list and skips the prompt.
- A non-empty selection writes project-local instruction files, .mcp.json aimed at the Zuplo docs MCP endpoint, and Claude settings that enable project MCP servers and the zuplo/tools GitHub marketplace.
- For agents other than Claude, the CLI downloads the zuplo/tools tarball from GitHub, rejects bodies over 10MB, and copies only SKILL.md files into the new project.
- The None choice and an empty agent list skip those writes.
- The tarball filter keeps only SKILL.md paths and the temp directory is removed afterward.
- No credential harvesting, install-time execution, or self-dependency lifecycle chain was found in the inspected entry.
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.1.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.8.1 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.