@datadog/ai-setup-cli@2.0.35
Interactive tool for Datadog setup
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s verification flow launches a project-controlled dev script without a separate confirmation and passes it the full CLI environment. This creates a real secret-exposure risk, although the feature is scoped to interactive RUM verification and no malicious collection or transmission is shown in the package source.
Decision evidence
public snapshot- After successful setup, non-headless browser-RUM runs start telemetry verification unless the user has cancelled.
- Verification starts the project’s package-manager `dev` script and passes it the full inherited `process.env`.
- It runs `chrome-devtools-mcp@latest` through `npx` and loads the project on an ephemeral localhost port.
- The feature is scoped to interactive products whose profiles inject real credentials; the stated purpose is to verify RUM beacons.
- The verification runs after the setup flow and is limited to browser-RUM products in interactive mode.
- The browser load is directed to the project’s local server, and the expected telemetry is RUM beacon traffic.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
bin/cli.cjsView on unpkg · L15Source writes installer persistence such as shell profile or service configuration.
Findings
Affected versions and remediation
This report applies to @datadog/ai-setup-cli@2.0.35.
See all versions of @datadog/ai-setup-cli for other recorded verdicts.
- Review the evidence and your use of @datadog/ai-setup-cli@2.0.35 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.