Contact

Reporting a bug

The most useful report includes the tool you were using, what you pasted (or a small example that reproduces it), what you expected, and what happened instead. Browser and version help when it looks like a rendering issue.

Please do not send real credentials, tokens or customer data in a bug report. If a JWT is misbehaving, generate a token with the same shape and dummy values.

Requesting a tool

Worth saying what you are actually trying to do rather than just naming the tool — the underlying task often points at a better fit than the obvious one. Anything that fundamentally requires a server (DNS lookups, sending mail, fetching URLs) is out of scope by design.

Security

If you have found something that puts users at risk — a way to make a tool execute pasted input, a sanitiser bypass, anything of that shape — please report it privately first and give us a reasonable window to fix it. See the security page for scope.

Reaching us

Email hello@devtoolery.org. It is a small project, so replies are best-effort rather than guaranteed.