resend-cli@2.21.0
The official CLI for Resend
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner's command, environment, file, and network findings map to normal CLI functions, credential storage, update checks, and disclosed anonymous telemetry. Source inspection found no lifecycle trigger or concrete credential or command-output exfiltration.
Decision evidence
public snapshot- The package exposes a user-invoked CLI entrypoint and declares no install lifecycle hook.
- The CLI states that it collects anonymous usage data and provides an opt-out.
- Telemetry payload construction contains command metadata, platform, Node version, flags, and an anonymous identifier; it does not include API keys or credential-file contents.
- The detached child process only invokes this CLI's hidden telemetry flush command.
- Network use is aligned with the Resend API, update checks, and disclosed telemetry.
- No install-time execution, broad project mutation, credential exfiltration, or persistence was found.
Source & flagged code
9 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.21.0.
See all versions of resend-cli for other recorded verdicts.
- Review the evidence and your use of resend-cli@2.21.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.