resend-cli@2.20.0
The official CLI for Resend
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe critical scanner matches are explained by normal CLI API functionality and optional telemetry. Source inspection found no lifecycle hook or concrete path that sends user credentials or command output to an attacker-controlled receiver.
Decision evidence
public snapshot- The manifest exposes a user-invoked CLI binary and has no install lifecycle hook.
- The CLI sends opt-out anonymous usage telemetry after commands.
- No preinstall, install, or postinstall script is present.
- Telemetry records command names, versions, platform, and option names; it does not include the supplied API key or command output.
- Credential storage and API calls are explicit CLI features rather than install-time behavior.
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.20.0.
See all versions of resend-cli for other recorded verdicts.
- Review the evidence and your use of resend-cli@2.20.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.