Contact
Toolhub has no contact form. The site has no backend by design — there is no server-side database to receive submissions, no email pipeline to log correspondence, no CRM to feed. Communication runs through two public, well-understood channels: GitHub Issues and email.
This page covers which channel suits which kind of request, what gets prioritised, and what Toolhub does not offer.
GitHub Issues — preferred for most things
For bug reports, feature requests, translation corrections, new tool proposals, and general questions, GitHub Issues is the right channel:
https://github.com/JXXR1/Toolhub/issues
Issues are preferred because the discussion lives at a permanent URL. Other people running into the same bug, asking the same question, or proposing the same tool can find the existing thread and add their own context rather than starting from scratch. The result is faster triage and better-documented fixes.
Useful information to include when opening an issue:
- Which tool the issue affects (URL is fine)
- Which browser and operating system
- What was tried and what happened (screenshots help)
- Expected vs actual behaviour
Toolhub accepts issues in any language. English gets the fastest response simply because no translation step is needed; issues in other languages are still read and triaged but may take longer.
Email — for things that don't fit Issues
Email is the right channel for cases where a public thread is not appropriate:
It is the right destination for:
- Security disclosures (see below)
- Press, partnership, or licensing enquiries
- Takedown or DMCA notices
- Anything involving personal data or confidential information
Security disclosures
Toolhub follows a 90-day responsible-disclosure window. To report a security issue, email contact@toolhub.software with "SECURITY" in the subject line. Acceptable proofs include a minimal reproduction, browser DevTools recordings, or a brief write-up.
The site is browser-only — no user input is sent to a backend — so most classical web-application vulnerabilities do not apply. The threat surface is mainly third-party libraries pulled in by the build, XSS in markdown rendering, and the small set of fetch calls documented per tool. Reports that focus on those areas are likely to land cleanly.
What Toolhub does not offer
Setting expectations honestly:
- No service-level agreement or guaranteed response time
- No commercial support tier or paid priority queue
- No phone or chat channel
- No custom integrations or white-label arrangements
Most issues are triaged within a week. Security reports are read sooner. Feature requests are tracked but not committed to.