Contact Honest UI

Search the existing GitHub issues before opening a new report. If the problem has not been reported, open a GitHub issue with the affected Honest UI version, your React and Node.js versions, the command or component involved, reproduction steps, and the result you expected. A small repository or code example is useful when the failure depends on project configuration.

GitHub issues are public. Do not include access tokens, private repository content, personal data, customer information, unpublished source, or security-sensitive details. Remove secrets from logs and screenshots before attaching them.

Do not report a suspected vulnerability in a public issue, discussion, or pull request. Use GitHub private vulnerability reporting. Include a clear description, affected versions, reproduction steps or a proof of concept, and the impact you believe the vulnerability has. The project security policy explains the supported version and disclosure process.

Small bug fixes and documentation improvements can go directly to a pull request. Open an issue before beginning a large change or new component so the approach can be discussed first. The contribution guide lists the local setup, required checks, accessibility expectations, and the information to include with a pull request.