telnyx-voice-conferencing-go
Fail
Audited by Snyk on Mar 12, 2026
Risk Level: HIGH
Full Analysis
HIGH W008: Secret detected in skill content (API keys, tokens, passwords).
- Secret detected (high risk: 1.00). I scanned the full prompt for literal, high-entropy values that could provide access.
Flagged item:
- The string "v3:MdI91X4lWFEs7IgbBEOT9M4AigoY08M0WWZFISt1Yw2axZ_IiE4pqg" appears multiple times as a CallControlID/connection identifier. It is long, random-looking, and the docs explicitly state call_control_id / connection_id are used to issue commands via the Call Control API — meaning this literal could be a usable credential. Because it is a high-entropy literal present in the documentation, it meets the "secret" definition.
Ignored items and why:
- UUIDs such as "182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e" and "c46e06d7-b78f-4b13-96b6-c576af9640ff" are resource identifiers (low-entropy, standard UUID format) and do not by themselves meet the definition of a secret here.
- TELNYX_API_KEY is referenced via os.Getenv("TELNYX_API_KEY") — no literal API key is present.
- Simple example values like "1234#" or "support" or "tier_1_support" are low-entropy examples/placeholders and intentionally ignored per the rules.
Because the v3:... token is a high-entropy literal used as a call control/connection id (and could be abused to issue commands), it should be treated as a secret.
Issues (1)
W008
HIGHSecret detected in skill content (API keys, tokens, passwords).
Audit Metadata