@wraps.dev/cli@3.17.4
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 9d ago · by lpm-firewall-aiThe configurable API destination permits conditional forwarding of a saved service token to an unrelated receiver, which warrants a warning. The default destination is package-aligned, and the reviewed manifest has no install lifecycle hook.
Decision evidence
public snapshot- The connect command can load a saved Wraps token and pass it into the authenticated connection flow.
- The connection request sends that token as a bearer credential with account and organization data.
- The API destination can be overridden with WRAPS_API_URL; its default is the Wraps API host.
- The self-hosted branch uses the self-hosted API URL and resolves a token for that service.
- The manifest lists no npm install lifecycle hook.
- The default API destination is https://api.wraps.dev, consistent with the CLI’s service.
- The self-hosted connection path selects the configured self-hosted API and its instance token.
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.17.4.
See all versions of @wraps.dev/cli for other recorded verdicts.
- Review the evidence and your use of @wraps.dev/cli@3.17.4 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.