Skip to content
+

Support

Use GitHub to report bugs, request improvements, and help the maintainers understand what your team needs from Open UI Kit.

GitHub

We use GitHub issues for bugs, feature requests, and documentation improvements.

Before opening a new issue:

  1. Search the existing issues to avoid duplicates.
  2. Check whether the behavior is already covered in the docs or Storybook.
  3. Prepare a small reproduction when the issue is related to runtime behavior or styling.

Open a new issue in the Open UI Kit repository.

Bug reports

Good bug reports usually include:

  • The Open UI Kit, React, and peer dependency versions.
  • The browser and operating system where the issue appears.
  • A minimal reproduction or code snippet.
  • Expected behavior and actual behavior.
  • Screenshots or recordings for visual regressions.

Feature requests

For new components or API changes, explain the product problem first. Examples from a real workflow are more useful than a list of props, because they help the library keep the right level of abstraction.

Questions

For implementation questions, prefer GitHub Discussions when available. If the answer should become part of the docs, open a documentation issue so it can be tracked and added here.

Security issues

Do not open public issues for suspected vulnerabilities. Use GitHub private vulnerability reporting for the repository and include the affected versions, reproduction steps, and any known mitigations.

Maintainers aim to acknowledge security reports within three business days, then follow up with next steps within an additional three business days.