create-zuplo-api@7.7.7
Create Zuplo API with one command
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package has no automatic npm lifecycle trigger or confirmed credential theft. Its explicit agent setup writes AI-agent control files and fetches remote skills, which is a real but user-invoked capability risk under the stated policy.
Decision evidence
public snapshot- The user-invoked CLI can write MCP and AI-agent instruction files into the newly created project.
- When AI agents are selected, it downloads skills from a GitHub tarball and installs them into agent-specific project folders.
- The CLI sends invocation telemetry to PostHog unless the user sets its opt-out environment variable.
- It can run the selected package manager to install dependencies in the new project.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The agent configuration is selected through the CLI's --agents option or interactive prompt, rather than during package installation.
- The telemetry payload contains generated and package-manager usage data, not harvested environment values or files.
- The child-process use is for normal project dependency installation and optional Git initialization.
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.7.7.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.7.7 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.