Use GitHub Private Vulnerability Reporting to send vulnerability details securely to the repository maintainers.

Do not disclose vulnerability details in a public issue, discussion, pull request, or other public channel.

A useful private report should contain the affected component and version, impact, minimal reproduction steps, and any proposed mitigation.

Do not include private machine data or sensitive logs and screenshots in a report. Replace sensitive values with clearly marked placeholders and retain originals locally.

Report privately when the behavior could expose private data, bypass the loopback-only boundary, execute unintended commands, or affect systems beyond the user's intended Media Control for D200 operation.

Crashes, display errors, setup problems, and incorrect behavior without a confidentiality, integrity, or boundary impact are ordinary bugs. Report them through the public issue tracker using a minimal reproduction that contains no secrets.