Security

Last updated: 2026-11-05

Reporting a vulnerability

Please do not open a public issue for a security problem. Email support@snipedex.org with:

  • the affected endpoint or component, and a proof of concept or steps to reproduce it,
  • the impact as you understand it (data exposed, privilege escalation, and so on),
  • whether the issue has been shared with anyone else or disclosed publicly.

What to expect

  • An acknowledgement within 3 business days.
  • An initial assessment (severity, affected scope) within 7 business days.
  • A fix as soon as it is ready for critical issues, since fixes go out through the normal deploy pipeline; we give you a concrete estimate once the report is assessed.
  • Status updates at least weekly until it is resolved, even if the update is “still working on it”.

Supported versions

Snipedex is a continuously deployed hosted service, not a versioned library. Security fixes land on the live service itself; there are no older maintained versions.

Coordinated disclosure

  • Please give us a reasonable window to ship a fix before you disclose anything publicly: 90 days from our acknowledgement, longer if we are actively working on it and keeping you informed.
  • Test only against your own account and workspace. Do not access, change or copy other people's data, and do not run automated scans that slow the service down for others.
  • We will not pursue legal action against good-faith research that follows this policy.
  • We credit you in the fix's release notes if you wish; otherwise reporters stay anonymous.