create-zuplo-api@7.12.1
Create Zuplo API with one command
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or confirmed attack behavior. Agent configuration is optional and selection-driven, while analytics sends usage metadata to a package-aligned endpoint and can be disabled with ZUPLO_DO_NOT_TRACK.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the CLI and declares build and test scripts, with no install lifecycle hook.
- Agent setup is optional: the CLI asks which agents to configure, and writes configuration only when the selection is nonempty. The files target the new project, and optional skills come from Zuplo’s tools repository.
- The CLI sends an opt-out-gated creation event with version and selected options; its package-manager metadata is limited to package-manager, runner, install-source, Node, platform, and architecture fields.
- The CLI downloads agent skills and writes agent configuration files, but this occurs as part of project creation after agent selection.
- The bundle uses network and environment APIs for package-aligned setup and usage analytics; inspected code does not show credential collection or disclosure.
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.12.1.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.12.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.