@wraps.dev/cli@3.11.1
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 reachable token-to-unrestricted-endpoint flow is a real dangerous capability, although it requires an explicit environment override and command execution. It warrants a warning rather than a block because no automatic or hidden exfiltration path was found.
Decision evidence
public snapshot- The manifest exposes dist/cli.js as the wraps command-line entrypoint.
- An authenticated session token is selected from saved auth configuration even when WRAPS_API_URL disables the self-hosted-instance selection.
- API requests interpolate the selected base URL and attach that token as a Bearer credential.
- The manifest declares no preinstall, install, or postinstall lifecycle hook.
- The credential forwarding requires a user to run an authenticated command with WRAPS_API_URL set; no hidden default recipient was found.
Source & flagged code
13 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.11.1.
See all versions of @wraps.dev/cli for other recorded verdicts.
- Review the evidence and your use of @wraps.dev/cli@3.11.1 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.