The fastest way to reach us is email: hello@nxtolerance.com.

What to write about

Parser bugs (highest priority). If valid JSON is rejected — or invalid JSON passes — tell us the smallest input that reproduces it. If the JSON is sensitive, redact the values ("name": "x" works fine); the bug lives in the structure, not your data. Please include the error message and position the tool reported.

Confusing error messages. If a message sent you looking in the wrong place, that counts as a bug too. “The tool said expected ‘:’ but the real problem was a missing comma one line up” is exactly the kind of report that improves the messages for everyone.

Feature requests. Reasonable asks we’ve heard: YAML→JSON conversion, JSONPath querying, diffing two documents. If you keep reaching for something the tool doesn’t do, describe the workflow — how you got the JSON and what you needed to do with it is more useful than a bare feature name.

Everything else. Broken pages, accessibility issues, partnership requests, corrections to the JSON5 or JSON Schema articles. Please include the URL of the page you’re writing about.

What to expect

We’re a small team and read every message. Bug reports with a reproduction case are usually answered within a few days; general feedback may take longer. No ticket system, no automated replies — a person reads and answers your email.