1.2 KiB
Security policy
The current supported line is 0.1.x. Older snapshots and untagged forks do not
receive security fixes.
Do not open a public issue for a suspected vulnerability. Use the repository host's private security-advisory/reporting interface when available. Otherwise, contact the repository owner privately through the hosting profile and request a secure channel. Include the affected version/commit, operating system, impact, minimal reproduction, and whether details have been shared elsewhere. Do not include private documents processed by John Slop.
The maintainer will acknowledge a report within seven days, assess scope and severity, coordinate a fix and disclosure date when confirmed, and credit the reporter if requested. This is a best-effort volunteer response target, not a service-level guarantee.
John Slop processes untrusted text and archives but is not a sandbox. Archive limits and path validation reduce exposure; reports that bypass those limits, cause unintended writes, leak document contents, corrupt protocol output, or execute code are in scope. False-positive disagreements and requests for new heuristics belong in the normal issue tracker.