@mastra/datadog@1.4.6
Datadog LLM Observability exporter for Mastra - exports tracing data to Datadog's LLM Observability product
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a conventional observability integration with no lifecycle execution or malicious primitives. Environment-variable use configures Datadog tracing only after the exporter is constructed.
Decision evidence
public snapshot- The manifest has no install lifecycle hook and declares only Datadog and Mastra runtime dependencies.
- The entrypoint imports dd-trace and exports Datadog tracing exporter classes.
- The exporter requires an application name and, in agentless mode, an API key before enabling tracing.
- Runtime handling emits application spans through the Datadog tracer; this matches the package purpose.
- No child-process, shell, filesystem, eval, native-loading, or persistence code was found in the package artifacts.
- The dynamic import only loads the paired Mastra observability module for feature compatibility.
- No package source directly performs network requests or contains an opaque payload endpoint.
Source & flagged code
6 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/index.jsView on unpkg · L2The entrypoint imports dd-trace and exports Datadog tracing exporter classes.
dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @mastra/datadog@1.4.6.
See all versions of @mastra/datadog for other recorded verdicts.
- Review the evidence and your use of @mastra/datadog@1.4.6 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.