resend-cli@2.17.0
The official CLI for Resend
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic hints conflate normal CLI credential storage, operating-system keychain access, and disclosed telemetry with exfiltration. Source inspection found no lifecycle-triggered execution, credential theft, command-output exfiltration, or persistence.
Decision evidence
public snapshot- The package exposes only a user-invoked resend command and has no npm lifecycle hook.
- The bundled CLI discloses anonymous usage telemetry and provides an opt-out.
- Credentials are documented as user-provided local authentication for Resend commands.
- No install-time execution or foreign AI-agent configuration writes were found.
- Child-process use is limited to command dispatch, browser opening, and operating-system credential stores.
- The reported network activity is Resend API use, update checking, and disclosed telemetry; no command output or credentials are sent to an unrelated receiver.
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.17.0.
See all versions of resend-cli for other recorded verdicts.
- Review the evidence and your use of resend-cli@2.17.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.