Security guidance

Report carefully.
Keep sensitive details private.

Use this page to choose the right reporting route for a CodeWorksLabs site or product. Please do not publish credentials, personal data, private vulnerability details, or working exploit material in a public issue.

Private report

Potential vulnerability

Email a concise description, the affected product or hostname, observed impact, and safe reproduction details. Remove secrets and unnecessary personal data before sending.

Email security

Product routes

Use canonical guidance

Product-specific instructions take precedence when they exist. Brand Navigation maintains dedicated disclosure guidance; DiscussionBridge retains its independent support and product identity.

Public issues are for non-sensitive defects.

If a report could expose users, systems, credentials, private configuration, or an unpatched weakness, begin privately. CodeWorksLabs will route the report to the responsible product or site owner without claiming a response time that has not been formally established.