@wraps.dev/cli
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.
This report shows the evidence for @wraps.dev/cli@3.20.1. 0 of 32 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 17h ago · by lpm-firewall-aiThe flagged behavior is consistent with an AWS deployment CLI: the metadata access is AWS SDK credential-provider code, and the curl-to-shell match is printed installation guidance. Runtime telemetry is sent to the package service with an opt-out, and the manifest has no install hook.
Decision evidence
public snapshot- The manifest describes an AWS infrastructure deployment CLI and exposes dist/cli.js as its main entry and wraps executable.
- The package scripts contain build and test commands but no install lifecycle hook.
- The metadata access is part of AWS credential-provider logic that requests an IMDSv2 token, consistent with the package's AWS purpose.
- Runtime telemetry goes to wraps.dev and the CLI displays an opt-out command.
- The flagged curl-to-shell text appears in a Pulumi installation troubleshooting message; no automatic execution is shown in that excerpt.
- Telemetry is sent to the package's service and can be disabled.
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.
Findings
Affected versions and remediation
This report applies to @wraps.dev/cli@3.20.1.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @wraps.dev/cli@3.20.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.