resend-cli@2.19.0
The official CLI for Resend
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe high-risk scanner matches are explained by an email-service CLI, optional telemetry, credential storage, and explicitly invoked API operations. Source inspection found no install hook or concrete exfiltration of credentials or command output.
Decision evidence
public snapshot- The command-line program records anonymous usage telemetry unless the documented opt-out environment variable is set.
- The package exposes a CLI binary and has no install lifecycle hook.
- Telemetry contains command, version, operating-system, Node version, interaction mode, installation method, and flag names; it does not include the Resend credential.
- The only confirmed telemetry receiver is PostHog; API traffic is directed to the Resend API.
- Child-process use launches the CLI's own telemetry flush command or opens a user-requested browser.
- No credential harvesting, arbitrary command-output upload, install-time execution, or foreign configuration mutation was found.
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.19.0.
See all versions of resend-cli for other recorded verdicts.
- Review the evidence and your use of resend-cli@2.19.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.