trace-analytics Audit report.

Warnings

• Dependency or permission surface needs review
• Permission surface may require sandboxing
• PPL query templates embed user-supplied values such as <TRACE_ID> directly into query strings; a malicious trace ID or field value could inject additional PPL clauses if not escaped or validated.
• Service map query uses nested struct fields like sourceNode/targetNode but does not show how to extract keyAttributes.name, which can produce hard-to-read output.
• The query templates are not guaranteed to have been validated against a live cluster; the skill correctly instructs verification when an endpoint is available, but this review could not confirm runtime behavior.
• Quality score needs review
• Permission surface needs review: secrets or environment access, shell or command execution
• GitHub adoption: 52 GitHub stars
• Stars/forks activity: 52 stars, 52 forks; issue activity unavailable in current metadata
• Dependency/runtime risk: credential or environment access, network or browser surface
• Permission surface: secrets or environment access, shell or command execution

Method

This report combines public metadata, AI review output, repository freshness, install readiness, OpenAgentSkill events, quality scoring, trust checks, and the agent safety gate. It is not a full source-code security review.