create-zuplo-api@7.12.6
Create Zuplo API with one command
AI Security Review
scanned 14d ago · by lpm-firewall-aiSource inspection found no lifecycle hook and no confirmed attack in the active CLI path. The flagged token-transfer helper has no caller in the inspected bundle; the reachable analytics event sends setup metadata and can be disabled with ZUPLO_DO_NOT_TRACK.
Decision evidence
public snapshot- package.json exposes dist/index.js as the CLI and declares no lifecycle hook.
- The CLI sends opt-out-controlled analytics to app.posthog.com.
- The analytics event contains setup choices and package version, with no credentials or environment values in the event properties.
- The bundle contains code that reads a saved Zuplo token and sends it to an environment-configurable API endpoint, but source searches found no callers of that token-reading or account-fetching helper.
- The manifest’s bin points to the CLI; the token-transfer helper appears only as a definition in the inspected bundle, with no activation path found.
- No install-time behavior or confirmed credential transfer from the active CLI path was identified.
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.6.
See all versions of create-zuplo-api for other recorded verdicts.
- Review the evidence and your use of create-zuplo-api@7.12.6 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.