Skip to content

Security: mazidul36i/dev-tools

Security

SECURITY.md

Security Policy

Supported Versions

We currently provide security updates for the following versions of DevTools:

Version Supported
0.0.1

As the project matures, this table will be updated to reflect the supported versions.

Reporting a Vulnerability

We take the security of DevTools seriously. If you believe you've found a security vulnerability, please follow these steps:

  1. Do not disclose the vulnerability publicly
  2. Email the security team at islammazidul1369@gmail.com with details of the issue
  3. Include the following information:
    • 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 the issue

Response Process

Our security team will acknowledge your email within 48 hours and provide an estimated timeline for a fix. We follow these steps:

  1. Confirm the problem and determine the affected versions
  2. Audit code to find any similar problems
  3. Prepare fixes for all supported versions
  4. Release new security patch versions

Disclosure Policy

When we receive a security bug report, we will:

  • Confirm the problem and determine the affected versions
  • Fix the problem and prepare a security advisory
  • Release the fix to the public, along with credit to the reporter (unless they prefer to remain anonymous)

Comments on This Policy

If you have suggestions on how this process could be improved, please submit a pull request or open an issue to discuss.

There aren't any published security advisories