resend-cli@2.24.0
The official CLI for Resend
AI Security Review
scanned 21d ago · by lpm-firewall-aiSource inspection found default usage telemetry with a bounded event schema and explicit opt-outs, but no concrete attack behavior. The scanner's execution and persistence indicators correspond to CLI functionality rather than an install-time attack.
Decision evidence
public snapshot- package.json exposes dist/cli.cjs as the CLI and has no install lifecycle hook; its listed prepack script builds the bundle.
- The bundle queues a cli.used event with command, version, platform, Node version, interaction status, install method, and flag names.
- The telemetry path is called after a regular CLI command; update and telemetry commands are excluded.
- The bundle validates the usage event and sends it to the Resend CLI's PostHog collector.
- DO_NOT_TRACK=1 and RESEND_TELEMETRY_DISABLED=1 disable telemetry.
- Usage telemetry is enabled by default and stores an anonymous identifier locally.
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.24.0.
See all versions of resend-cli for other recorded verdicts.
- Review the evidence and your use of resend-cli@2.24.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.