@datadog/ai-setup-cli@2.0.33
Interactive tool for Datadog setup
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe new local MCP server supports workspace setup and applies workspace and sensitive-file boundaries. Credential and network references are consistent with Datadog authentication, and environment scanning returns metadata rather than values.
Decision evidence
public snapshot- The package is an interactive Datadog setup CLI with normal CLI and library entry points.
- The new local MCP tools restrict file reads and edits to the workspace and exclude Git metadata and sensitive dotfiles.
- Environment-file scanning reports variable names and whether values are present; it does not return the values.
- Datadog API credentials are used to create a Datadog client for setup tools, and the CLI routes agent authentication through the Datadog gateway.
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.33.
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.33 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.