Acknowledgements

Thank You

Jynx is built by a very small team. When someone outside that team takes the time to make the platform better — by reporting a security issue, flagging a bug, improving a translation, or contributing in any other way — we think that deserves to be said out loud and in public.

This page is where we say it. It is permanent, and it is the standing offer: if you contribute something we act on, we will credit you here, with the name or handle you choose.

Security Research

People who have reported a confirmed, in-scope security issue under our Security & Vulnerability Disclosure Policy, and consented to being named. Entries are added once the corresponding fix is live.

• Yaseen Zubair — DNS & email configuration hardening — August 2026

Other Contributions

Bug reports, usability feedback, translation corrections, and community contributions that led to a change in the product.

• No entries published yet.

How to Be Credited

1. Report it. Security issues go to [email protected] — please read the disclosure policy first, particularly the out-of-scope list. Everything else goes to [email protected].
2. Tell us how you want to appear. Your real name, a handle, or an organisation — whatever you prefer. Include a link (personal site, profile) if you would like one, or tell us you would rather have none.
3. We ship the fix. Entries go up after the change is live, not before.
4. We add you here. If you later want your entry changed or removed, email us and we will do it.

Credit is described by contribution category — for example "DNS & email configuration hardening" — rather than by the technical detail of any individual finding. That keeps the page useful to you as a public record without turning it into a map of past weaknesses.

What We Do Not Offer

Jynx does not run a paid bug bounty programme and does not pay for reports. Recognition on this page is what we offer, and we offer it sincerely. See the Security & Vulnerability Disclosure Policy for the full position.