resend-cli@2.16.0
The official CLI for Resend
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect inspection shows no install-time execution or credential/command-output exfiltration. Scanner findings conflate package-aligned API use and bounded telemetry with malicious behavior.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall hook.
- The bin entry is the user-invoked dist/cli.cjs CLI.
- Telemetry records command metadata, OS, Node version, interactivity, and flags; it does not include API keys.
- Telemetry POSTs only the defined cli.used event to PostHog and honors DO_NOT_TRACK or RESEND_TELEMETRY_DISABLED.
- API calls target the Resend API for the CLI's stated email-management functionality.
- child_process use launches the CLI telemetry flush and Commander subcommands, not harvested-command execution.
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.16.0.
See all versions of resend-cli for other recorded verdicts.
- Review the evidence and your use of resend-cli@2.16.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.