Skip to content

Latest commit

 

History

History
46 lines (28 loc) · 1.83 KB

SECURITY.md

File metadata and controls

46 lines (28 loc) · 1.83 KB
Raw

Security Policy

Supported Versions

dynssz is currently in active development and has not reached a stable release yet. The library is functional and being improved on an ongoing basis, but it may be considered unstable. While testing and feedback are greatly appreciated, using it in production environments is recommended with caution.

Version Supported
dev ✅

Reporting a Vulnerability

I take the security of the dynssz library seriously. If you believe you have found a security vulnerability in dynssz, please report it to me in a responsible manner.

Please do not report security vulnerabilities through public GitHub issues.

How to Report a Security Vulnerability?

For critical security issues, please contact me privately:

  • Matrix: @pk910:matrix.org
  • Twitter: @_pk910_
  • Discord: pk910 (find me at EthStaker or ETH R&D communities)

I appreciate your effort to responsibly disclose your findings.

What to Include in Your Report?

Your report should include:

  • The conditions under which the vulnerability occurs.
  • Detailed steps to reproduce the vulnerability.
  • Any relevant logs, error messages, or outputs.
  • If possible, a proof-of-concept or exploit code.

What to Expect After Reporting a Vulnerability?

Upon receiving a report of a vulnerability:

  • I will assess the vulnerability for its veracity and potential impact.
  • I may contact you for further information.
  • I will work on addressing the issue and keep you updated on the progress.

I aim to collaborate with the security community to identify and resolve vulnerabilities responsibly. I will keep the community informed of security issues that may arise during the development process.

Thank you for helping ensure the security and reliability of dynssz.