Skip to content

Security: anxin233/gitviz

Security

SECURITY.md

Security Policy

πŸ”’ Supported Versions

We release patches for security vulnerabilities in the following versions:

Version Supported
1.0.x βœ…

πŸ› Reporting a Vulnerability

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

Please do NOT:

  • Open a public GitHub issue
  • Disclose the vulnerability publicly before it has been addressed

Please DO:

  1. Email the details to the repository maintainers (check GitHub profile for contact)
  2. Include the following information:
    • Type of vulnerability
    • Full paths of source file(s) related to the vulnerability
    • Location of the affected source code (tag/branch/commit or direct URL)
    • 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

What to expect:

  • We will acknowledge your email within 48 hours
  • We will provide a more detailed response within 7 days
  • We will work on a fix and release it as soon as possible
  • We will credit you in the release notes (unless you prefer to remain anonymous)

πŸ›‘οΈ Security Best Practices

When using GitViz:

  • Only analyze repositories you trust
  • Be cautious when sharing generated HTML files as they may contain sensitive commit messages
  • Keep GitViz updated to the latest version
  • Review the generated visualizations before sharing publicly

πŸ“œ Disclosure Policy

When we receive a security bug report, we will:

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

Thank you for helping keep GitViz and its users safe!

There aren't any published security advisories