Skip to content

Security: NhanAZ/libBedrock

SECURITY.md

Security Policy

Supported Versions

Version Supported
< Lastes version
Latest

Reporting a Vulnerability

DO NOT report vulnerabilities on the GitHub issue tracker. GitHub is public and anyone can see the issues you post on the issue tracker, including people who would exploit vulnerabilities for their own gain.

WARNING: You may put live servers at risk by reporting a vulnerability on the GitHub issue tracker.

Contact me by sending an email to nhanaz@duck.com. Include the following information:

  • Version of libBedrock
  • Detailed description of the vulnerability (e.g. how to exploit it, what the effects are)
  • Your GitHub username, if you wish to be credited for reporting the problem in the security advisory

Please note that i can't guarantee a reply to every email.

FAQ

Do you offer a bug bounty?

No.

How soon can I expect a fix for a vulnerability I've reported?

This depends on the nature of the problem. I can't provide any general ETA (nor would it be wise to provide one). In general, it depends on when developers have time to look into the problem, how complex the problem is to fix, and how many users it impacts.

When a fix for a severe vulnerability is pushed, a patch release for the target version will usually be released within 24 hours so that users can update.

There aren’t any published security advisories