telnyx-voice-conferencing-python

Fail

Audited by Snyk on Mar 16, 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 prompt for literal, high-entropy values that could grant access. I found a repeated, long, random-looking token:
  • v3:MdI91X4lWFEs7IgbBEOT9M4AigoY08M0WWZFISt1Yw2axZ_IiE4pqg

Why this is flagged: it is high-entropy, random-looking, and used as a call_control_id in examples — a value that the docs say is used to issue Call Control API commands. Such a value could be a usable credential/token and should be treated as a secret.

I did NOT flag the following (and why):

  • api_key=os.environ.get("TELNYX_API_KEY") — environment variable name only (ignored).
  • UUIDs like 182bd5e5-6e1a-4fe4-a799-aa6d9a6ab26e and c46e06d7-b78f-4b13-96b6-c576af9640ff — resource IDs/UUIDs (not high-entropy secrets by the doc rules).
  • Placeholders and obvious examples: "call_control_id", "conference_id", "queue_name", "support", "tier_1_support", digits like "1234#" used for DTMF — these are placeholders or low-entropy/test values and intentionally ignored per the guidelines.

Recommendation: remove or rotate the v3:... token if it is real, and replace with a non-sensitive placeholder (e.g., "CALL_CONTROL_ID_EXAMPLE") in public docs.

Issues (1)

W008
HIGH

Secret detected in skill content (API keys, tokens, passwords).

Audit Metadata
Risk Level
HIGH
Analyzed
Mar 16, 2026, 10:36 AM
Issues
1