resend-cli@2.15.0
The official CLI for Resend
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic hints conflate legitimate CLI telemetry and child-process use with exfiltration. Source inspection shows no lifecycle execution and no flow of API credentials or command output to the telemetry endpoint.
Decision evidence
public snapshot- The manifest exposes a user-invoked resend executable and has no install lifecycle hook.
- The CLI's telemetry payload contains command metadata, version, operating system, Node version, interactivity, install method, and explicitly supplied flag names; it does not include API keys, command output, or credential contents.
- Telemetry can be disabled with RESEND_TELEMETRY_DISABLED=1 and is sent as a constrained cli.used event to PostHog.
- The telemetry send is reached after a CLI command completes, not during package installation.
- The CLI performs default anonymous usage telemetry to us.i.posthog.com.
- The bundle uses child-process APIs for credential-store integration and to detach the telemetry flush helper.
Source & flagged code
10 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to resend-cli@2.15.0.
See all versions of resend-cli for other recorded verdicts.
- Review the evidence and your use of resend-cli@2.15.0 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.