Contact
Bug reports, tool ideas, and security reports all go straight to the developer.
Before You Writeworktools.dev is built and maintained by one developer, so every message is read by the person who writes the code. Replies usually take a few business days. Emailing doesn't sign you up for anything.
1. How to Reach Me
Report a Bug
Wrong converter output, a broken layout, or a tool that won't load? Send the details below and I'll take a look.
Email support@worktools.devSuggest a Tool
Is there a tool you wish you could use without pasting data into someone else's server? Tell me what it should do.
Email support@worktools.devReport a Security Issue
Found a way around the Content Security Policy, an unexpected network request, or a script injection? Please report it privately.
Email security@worktools.devPrivacy Questions
Questions about what data the site handles or a request about your personal data? See the Privacy Policy, then get in touch.
Email support@worktools.dev2. What to Include in a Bug Report
The site has no error tracking, so I only learn about bugs when someone reports them. These details make a bug much quicker to fix:
- Browser and system: browser name and version (shown on the browser's About page) and your operating system.
- Page: the URL of the tool, for example
/dev/strapi-v4-v5-converter/. - Steps: what you did, what happened, and what you expected to happen.
- A small sample input: the smallest input that shows the problem.Remove any real credentials or customer data first.
- Console errors: any red messages in your browser's DevTools Console (F12).
3. Security Reports
- In scope: ways around the Content Security Policy, network requests that carry tool input, cross-site scripting, and inputs that crash or freeze a tool.
- Response: I aim to acknowledge reports within three business days and will keep you updated until the issue is fixed.
- Disclosure: please give me a reasonable chance to fix the issue before publishing details.