@datadog/ai-setup-cli@2.0.27
⚠ Under reviewInteractive tool for Datadog setup
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest and inspected callers do not establish an attack, but the selected @datadog/datadog-api-client dependency could not be inspected. This prevents a clean verdict under the dependency review policy.
Decision evidence
public snapshot- The manifest declares @datadog/datadog-api-client as a runtime dependency.
- dist/api/client.js imports that dependency for the package’s API client.
- The manifest’s scripts show no preinstall, install, or postinstall hook.
- The dependency source could not be inspected because its prepared package path was unavailable.
- The inspected source does not establish malicious behavior by this dependency.
- The flagged dev-server verifier is part of an interactive telemetry verification flow; it does not establish an attack.
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.27.
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.27 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.