Security model
JsonDrift’s core design is client-side processing: your JSON is not sent to our application servers for formatting, validation, or conversion. This reduces server-side data breach risk for tool inputs.
The site is delivered as static assets over HTTPS. Keep your browser updated for the latest security patches.
What we cannot protect
Malicious JSON or extremely large payloads could affect browser performance on your device. Do not paste secrets you are not willing to have in browser memory. Use dedicated secret managers for credentials.
Reporting a vulnerability
If you discover a security issue, please do not open a public GitHub issue.
Contact the maintainer privately with steps to reproduce, impact assessment, and any suggested fix. We aim to respond as soon as possible.
- Email: saifurrahmanshochib@gmail.com (subject: Security)
- GitHub: private security advisory if available on the repository
Safe harbor
We support responsible disclosure. We will not pursue legal action against researchers who report issues in good faith and allow reasonable time to remediate before public disclosure.