๐ Bug reports
Open a GitHub Issue. Include browser, OS, steps to reproduce, and a minimal JSON sample that triggers the bug.
Have a question, bug report, or feature idea? We'd love to hear from you.
Everything goes through GitHub Issues. Include your browser, OS, and steps to reproduce (or a sample JSON that triggers the issue, if it isn't sensitive).
Open an issue on GitHub โOr browse the existing issues first to see if your problem has already been filed.
Open a GitHub Issue. Include browser, OS, steps to reproduce, and a minimal JSON sample that triggers the bug.
Open a GitHub Issue with a clear title and example use case. Browse open issues first โ you can +1 an existing one instead of duplicating.
Use GitHub's private Security Advisories โ they let you report privately so we can patch before disclosure. Please don't open a public issue for vulnerabilities.
Open a GitHub Issue with the question label. We answer publicly so other users with the same question can find it later.
We monitor GitHub Issues regularly and typically respond within a few business days. Marked-urgent security advisories are handled fastest.
Yes โ please open an issue with the JSON that caused the problem (if it's not sensitive), the browser/OS you're on, and steps to reproduce.
The static site source is public on GitHub. All JSON processing happens in your browser โ you can verify exactly what the page does.