Get in touch

Email

[email protected]

This is a monitored address, and a real person reads it. It is the fastest route to us and the only one we guarantee to answer.

Reporting a wrong answer

A wrong answer from one of these tools is more important to us than a feature request, because a tool that gives a confident wrong result breaks somebody's build and they will not know why. If you send one, include:

• The tool you were using and the URL of its page.
• The input that produced the wrong result.
• What you expected and what you got instead.

You do not need to scrub the input before sending it — but please do scrub anything that is a live credential. The tools run locally precisely so that a secret never has to leave your machine, and a bug report is an exception you can avoid.

Requesting a tool

Tell us what you were trying to do, not just what you want built. The best requests we have received described a moment of friction — "I need to convert this payload into a form body and then check it against a schema" — and the tool that came out of it was more useful than the one that would have come from a feature list.

Response time

Usually within a few working days. A report that describes a wrong answer is prioritised over a feature request, and a request that blocks your work is prioritised over both.