Skip to content

Security: Pawankumar9090/TypeSync

Security

SECURITY.md

Security Policy

Supported Versions

Use this section to tell people about which versions of your project are currently being supported with security updates.

Version Supported
1.0.x
< 1.0

Reporting a Vulnerability

We take the security of TypeSync 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.

How to Report

If you have discovered a vulnerability, please email Pawan Kumar at pkuma7742@gmail.com with the subject line "TypeSync Security Vulnerability - [Issue Summary]".

Please include the following details in your report:

  • Type of vulnerability (e.g., cross-site scripting, SQL injection, remote code execution)
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept code or screenshots
  • Impact of the vulnerability

Response Timeline

We will acknowledge receipt of your report within 48 hours. We will then investigate the issue and communicate our findings to you. If the vulnerability is confirmed, we will work on a fix and release a security patch as soon as possible.

Credit

We appreciate the efforts of security researchers in helping us keep TypeSync secure. If your report results in a security fix, we will credit you in our release notes and changelog (unless you prefer to remain anonymous).

Thank you for helping keep TypeSync safe!

There aren’t any published security advisories