@wraps.dev/cli@3.17.5
⚠ Under reviewDeploy 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 8d ago · by lpm-firewall-aiThe inspected login flow is consistent with Wraps device authentication and caller-supplied API key storage. The inbound processor is a large minified bundle with unresolved behavior, so the source evidence does not support either a clean verdict or a confirmed attack.
Decision evidence
public snapshot- The manifest points the CLI entry to dist/cli.js.
- The authentication code uses the Wraps app URL for device authorization and polls for approval before saving the returned session token.
- The inbound processor is a 1.3 MB minified bundle; its full behavior remains unresolved in this review.
- The inspected login path stores an API key supplied through login options or a session token returned by device authorization.
Source & flagged code
14 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.17.5.
See all versions of @wraps.dev/cli for other recorded verdicts.
- Review the evidence and your use of @wraps.dev/cli@3.17.5 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.