opentelemetry

Pass

Audited by Gen Agent Trust Hub on Feb 17, 2026

Risk Level: SAFE
Full Analysis
  • [COMMAND_EXECUTION] (SAFE): The skill contains numerous shell commands for using helm, kubectl, curl, and otelcol. These commands are consistent with the primary purpose of managing OpenTelemetry infrastructure and validating connectivity within a Kubernetes environment.
  • [EXTERNAL_DOWNLOADS] (SAFE): External references for Helm charts and the OpenTelemetry Operator point to official sources (open-telemetry.github.io and github.com/open-telemetry). These are trusted organizations for this specific technology stack.
  • [DATA_EXFILTRATION] (SAFE): Telemetry pipelines are configured to send data to common backend endpoints (Prometheus, Loki, Tempo). The use of environment variables like ${env:MY_POD_IP} for configuration is a standard and safe practice for Kubernetes-native applications.
  • [REMOTE_CODE_EXECUTION] (SAFE): No malicious remote code execution patterns were detected. The auto-instrumentation methods described (e.g., using Java agents or Node.js --require) are the standard, documented ways to enable OpenTelemetry for applications.
  • [DATA_EXPOSURE] (SAFE): While the skill configuration involves reading container logs (/var/log/pods/*), this is the intended functionality of an observability collector. The RBAC rules provided follow the principle of least privilege required for OTel metadata enrichment.
Audit Metadata
Risk Level
SAFE
Analyzed
Feb 17, 2026, 05:59 PM