Contact
The project is maintained in public. The clearest route is the one that leaves enough context for someone else to reproduce the problem.
For general project questions, email [email protected]. OpenBrowse is maintained by Lucas Johnston Kurilov, who is also the contact for this website’s information-handling questions. The project source, issue history and release discussion live on GitHub. Before opening a report, check the documentation and search existing issues. If the problem concerns a self-hosted instance, include the version, operating system, the relevant error text and the smallest safe reproduction. Remove API keys, cookies, profile exports and any other credentials before posting.
Choose the right route
Start with setup, authentication and troubleshooting guidance before assuming a behaviour is a defect.
TroubleshootingUse a GitHub issue for a reproducible bug or a well-scoped feature request. Link to the exact release where possible.
Open issuesRead the implementation, releases and licence directly in the public repository. The website repository is separate from the runtime project.
Open sourceSensitive reports
Do not put a live credential, session cookie, profile storage state or a public exploit path in an issue. Check the repository’s security policy for the current private reporting channel. Until you have a safe channel, share only the minimum redacted information required to establish the impact.