@datadog/ai-setup-cli@2.0.30
Interactive tool for Datadog setup
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package's setup and authentication behavior is consistent with its purpose, but its default runtime telemetry can transmit a user's email and account identifiers without a disclosed telemetry opt-out. This is a privacy risk, not evidence of credential theft or malicious code execution.
Decision evidence
public snapshot- The CLI sends an `app_enter` telemetry event during startup.
- After authentication, telemetry context can include the Datadog user's ID, email, and name; the signup event builder forwards that email as `signupEmail`.
- Telemetry is sent to Datadog logs intake and the site's signup-event endpoint.
- The package is an interactive Datadog setup CLI, and its normal authentication and onboarding flows match that purpose.
- The README says headless use authorizes source-code upload and automatic command execution.
- No install lifecycle scripts are declared.
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.30.
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.30 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.