@wraps.dev/cli@3.5.3
Deploy email, SMS, and CDN infrastructure to your AWS account with one command. Sets up SES with DKIM/SPF/DMARC, event processing, and history automatically.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe scanner findings stem from a user-invoked AWS infrastructure CLI with default telemetry and bundled Lambda code. Source inspection found no lifecycle hook, hidden payload, credential transmission, or persistence outside its own configuration.
Decision evidence
public snapshot- The CLI posts usage telemetry to a Wraps endpoint when users run it.
- The bundled Lambda processor has network-capable code and was inspected.
- package.json has no preinstall, install, or postinstall hook.
- Telemetry payload contains command metadata, platform data, an anonymous ID, and optional organization ID; no credential values are included.
- AWS credential reads support AWS deployment validation and SDK operations.
- Auth tokens are saved only by the explicit auth login command with owner-only file permissions.
Source & flagged code
15 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L19A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/cli.jsFindings
Affected versions and remediation
This report applies to @wraps.dev/cli@3.5.3.
See all versions of @wraps.dev/cli for other recorded verdicts.
- Review the evidence and your use of @wraps.dev/cli@3.5.3 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.