Skip to content

Security: pyrevitlabs/pyRevit

SECURITY.md

Security Policy

Note that the most up to date code is located in the develop branch. Every 6 months to 12 months, the develop branch is merged to the master branch and new releases are integrated.

Reporting a Vulnerability

Please do not report security vulnerabilities through public pyRevit GitHub issues, discussions, or pull requests.

Instead, please send an email to eirannejad pyrevitsecurity[@]gmail.com .

Please include as much of the information listed below as you can to help us better understand and resolve the issue:

  • The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
  • 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

This information will help us triage your report more quickly.

There aren’t any published security advisories