registry / @wraps.dev/cli / 3.20.0
@wraps.dev/cli@3.20.0
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 3d ago · by lpm-firewall-aiThe inspected behavior matches the package’s stated AWS deployment purpose. Its telemetry is disclosed, limited to usage and runtime details, and has opt-out controls; the flagged link-local access is part of AWS credential resolution.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Telemetry runs in response to user-run CLI commands; AWS credential resolution occurs when AWS operations need it.
Impact
No evidence of credentials or project data being sent to an unrelated host, hidden execution, or harmful persistence was found.
Mechanism
Telemetry sends command events and basic runtime details to the Wraps endpoint. AWS credentials are resolved for AWS SDK operations, including standard instance metadata providers.
AI rationale
The inspected behavior matches the package’s stated AWS deployment purpose. Its telemetry is disclosed, limited to usage and runtime details, and has opt-out controls; the flagged link-local access is part of AWS credential resolution.
Evidence
wraps/workflows/cart-recovery.tswraps/workflows/welcome-sequence.tswraps/wraps.config.ts
Network endpoints5
wraps.dev/api/telemetry169.254.169.254169.254.170.2api.github.comapi.cloudflare.com
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a CLI for deploying email, SMS, and CDN infrastructure to AWS.
- Runtime telemetry reports command events and basic CLI, OS, Node, and CI details; the CLI identifies it as anonymous usage data and says it does not collect AWS credentials or email content.
- Telemetry can be disabled with DO_NOT_TRACK=1 or WRAPS_TELEMETRY_DISABLED=1.
- AWS credentials are used with AWS STS to validate the caller’s identity, consistent with the CLI’s stated purpose.
- The link-local metadata paths appear in the bundled AWS SDK credential provider.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationTelemetryUrlStrings
Source & flagged code
13 flaggeddist/cli.jsView file
19import { fileURLToPath } from "url";
L20: var getFilename, getDirname, __dirname;
L21: var init_esm_shims = __esm({
...
L272: // src/utils/shared/aws-detection.ts
L273: import { execSync } from "child_process";
L274: import { existsSync, readdirSync, readFileSync } from "fs";
...
L295: function detectCredentialSource() {
L296: if (process.env.AWS_ACCESS_KEY_ID && process.env.AWS_SECRET_ACCESS_KEY) {
L297: return "environment";
...
L338: const sts = new STSClient({ region: "us-east-1" });
L339: const identity = await sts.send(new GetCallerIdentityCommand({}));
L340: return identity.Account || null;
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cli.jsView on unpkg · L1919Trigger-reachable chain: manifest.main -> dist/cli.js
L19: import { fileURLToPath } from "url";
L20: var getFilename, getDirname, __dirname;
L21: var init_esm_shims = __esm({
...
L272: // src/utils/shared/aws-detection.ts
L273: import { execSync } from "child_process";
L274: import { existsSync, readdirSync, readFileSync } from "fs";
...
L295: function detectCredentialSource() {
L296: if (process.env.AWS_ACCESS_KEY_ID && process.env.AWS_SECRET_ACCESS_KEY) {
L297: return "environment";
...
L338: const sts = new STSClient({ region: "us-east-1" });
L339: const identity = await sts.send(new GetCallerIdentityCommand({}));
L340: return identity.Account || null;
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
2 Critical7 High5 Medium8 Low
CriticalHardcoded Runtime Data Exfiltrationdist/cli.js
CriticalTrigger Reachable Dangerous Capabilitydist/cli.js
HighChild Processdist/cli.js
HighShelldist/cli.js
HighCredential Redirect Persistencedist/cli.js
HighSandbox Evasion Gated Capabilitydist/cli.js
HighCloud Metadata Accessdist/cli.js
HighCross File Remote Execution Contextdist/cli.js
HighSemantic Analysis Limiteddist/lambda/inbound-processor/index.js
MediumDynamic Requiredist/lambda/agent-enforcer/index.js
MediumNetwork
MediumEnvironment Vars
Medium
Affected versions and remediation
This report applies to @wraps.dev/cli@3.20.0.
See all versions of @wraps.dev/cli for other recorded verdicts.
- Review the evidence and your use of @wraps.dev/cli@3.20.0 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.