Skip to content
DDevToolery

Reporting a problem

What to include, and what never to include.

Bug reports go to the address on the contact page.

What helps

  • Which tool, and the settings you had chosen.
  • A small example that reproduces it — the smallest input that still goes wrong.
  • What you expected and what happened instead.
  • Browser and version, if it looks like a display problem.

What not to send

Never include real credentials, tokens, customer data or anything confidential. If a JWT is behaving oddly, generate one with the same shape and dummy values — the token generator and the decoder together make that quick.

Security issues

Report privately first and allow a reasonable window before publishing. The security page describes what is in scope.

Wrong results

These are the most valuable reports. If a formatter produces output you believe is incorrect, include both the input and what you expected — a specific disagreement is much easier to act on than a general one.