create-zuplo-api@7.9.19
Create Zuplo API with one command
AI Security Review
scanned 25d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. Agent setup is selected in the CLI, while telemetry uses an analytics identifier and package-manager properties; the scanner’s credential and execution flags do not establish an attack.
Decision evidence
public snapshot- package.json exposes a CLI at dist/index.js and lists no install lifecycle hook.
- dist/index.js contains agent configuration paths for files including AGENTS.md and .mcp.json.
- The CLI asks interactively which AI coding agents to configure; CI or --yes mode selects none by default.
- Agent setup writes project configuration and skill files; the inspected code does not establish a malicious control-surface mutation.
- Telemetry sends a generated or stored analytics ID and package-manager usage properties to PostHog, not discovered environment credentials.
- The CLI performs network requests and uses child processes for ordinary project creation and repository setup.
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.9.19.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.9.19 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.