Contact

Toolhub has no contact form and no account system. The site has no backend by design — there is no server-side database to receive submissions and no CRM to feed. Communication runs through one well-understood channel: email.

This page covers which channel suits which kind of request, what gets prioritised, and what Toolhub does not offer.

Email — the way to reach Toolhub

For bug reports, feature requests, new tool proposals, corrections, and general questions, email is the channel:

contact@toolhub.software

Useful information to include in a bug report:

Email in any language is read and triaged; English gets the fastest response simply because no translation step is needed.

This is a monitored project inbox. It is the right destination for:

Security disclosures

Toolhub follows a 90-day responsible-disclosure window. To report a security issue, email the alias above 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:

Most issues are triaged within a week. Security reports are read sooner. Feature requests are tracked but not committed to.