create-zuplo-api@7.13.1
Create Zuplo API with one command
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no install hook, and the CLI's analytics request contains usage metadata rather than credentials. The credential-related helper is directed at the Zuplo developer API for account lookup, so the inspected source does not establish an unrelated recipient or concrete attack.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and lists development scripts, with no install lifecycle hook.
- The CLI sends a usage event containing package-manager, platform, and selected setup options to its analytics collector; it honors ZUPLO_DO_NOT_TRACK.
- The analytics identifier is generated locally, and the event data does not include an access token.
- The credential-related helper targets the Zuplo developer API for account lookup.
- Usage analytics are enabled by default unless ZUPLO_DO_NOT_TRACK is set.
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.13.1.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.13.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.