Skip to content

Security: flisk-sh/codeql-lobster

Security

SECURITY.md

Security Policy

This policy covers every repository in the flisk-sh organization that does not have its own SECURITY.md.

Reporting a vulnerability

Please do not open a public issue for security problems.

Report them privately, either:

  • through the repository's Security tab → Report a vulnerability (GitHub private vulnerability reporting), or
  • by email to hello@flisk.sh with "Security" in the subject.

Include the repository, the version or commit, steps to reproduce, and what an attacker could do with it.

What happens next

  1. Acknowledgement within 3 business days.
  2. Assessment and a severity estimate within 10 days.
  3. Fix within 30 days of confirming the problem, critical issues first. If it needs longer, we tell you why.
  4. Disclosure once a fix is released, with a GitHub security advisory that credits you unless you prefer otherwise.

Supported versions

Fixes go into the latest release of each project only. Please upgrade before reporting.

There aren't any published security advisories