Skip to content

Latest commit

 

History

History
44 lines (29 loc) · 1.72 KB

SECURITY.md

File metadata and controls

44 lines (29 loc) · 1.72 KB

Security Policy

Supported Versions

Currently supported versions with security updates:

Version Supported
1.0.x

Reporting a Vulnerability

We take the security of PDF Builder seriously. If you believe you have found a security vulnerability, please report it to us as described below.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to [email protected]. You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the following information in your report:

  • Type of issue (e.g., buffer overflow, SQL injection, cross-site scripting, etc.)
  • Full paths of source file(s) related to the manifestation of the issue
  • The location of the affected source code (tag/branch/commit or direct URL)
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit it

Preferred Languages

We prefer all communications to be in English.

Security Update Process

  1. The security report will be acknowledged within 48 hours
  2. We will confirm the issue and determine its severity
  3. We will develop and test a fix
  4. We will prepare a security advisory and release timeline
  5. We will notify users when a security release is scheduled
  6. Once the fix is verified, we will release it according to our release process

Comments on this Policy

If you have suggestions on how this process could be improved, please submit a pull request.