resend-cli@2.18.0
The official CLI for Resend
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection found no install-time execution, self-dependency chain, secret exfiltration path, or hidden persistence. The flagged network and child-process primitives are attributable to explicit CLI features and anonymous telemetry.
Decision evidence
public snapshot- The user-invoked CLI includes opt-out anonymous usage telemetry.
- package.json has no preinstall, install, postinstall, or prepare lifecycle hook.
- The only automatic entrypoint is the resend CLI binary.
- The bundled telemetry payload contains command metadata and flag names, not credential-file contents or command output.
- Credential storage, browser launch, local webhook forwarding, and shell completion writes are tied to explicit CLI features.
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.18.0.
See all versions of resend-cli for other recorded verdicts.
- Review the evidence and your use of resend-cli@2.18.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.