Stateless Tools

Channels

Recommended contact routes

If the issue tracker is unavailable, a public note through the repository or blog route is still better than a vague report with no reproduction details.

Bug Reports

What helps in a bug report

  • The tool page URL and the exact feature involved
  • A minimal reproducible input or sample
  • The expected result versus the actual result
  • Browser name/version and whether it happened on mobile or desktop
  • A screenshot or console error if available

Requests

What makes a feature request useful

Describe the workflow pain

“Add a tool” is less actionable than explaining which repetitive task you want to shorten.

Show expected input and output

Concrete examples help determine scope and implementation feasibility much faster.

Note whether browser-only is possible

It helps to know whether the feature can stay client-side or would depend on an external API.

Review priority

Issues in frequently used tools, confusing security copy, and mobile layout problems are reviewed first.