Skip to content

Security: ZeroMergeConflicts/HackTogether_01

Security

SECURITY.md

Security Policy

Reporting a Vulnerability

Please do not open a public GitHub issue for security vulnerabilities.

If you discover a potential security vulnerability in HackTogether_01, please report it privately through GitHub Private Vulnerability Reporting.

When submitting a report, please include:

  • A clear description of the vulnerability
  • Steps to reproduce the issue
  • The potential security impact
  • Affected files, components, or functionality
  • Proof of concept, if available
  • Any suggested mitigation or fix, if known

Please avoid publicly disclosing the vulnerability until it has been reviewed and addressed.

What to Report

Examples of security issues include:

  • API keys, tokens, or credentials being exposed
  • Unauthorized access to files or data
  • Authentication or authorization bypasses
  • Prompt injection leading to unintended actions or data exposure
  • Path traversal or unsafe file handling
  • Sensitive information being stored or exposed unintentionally
  • Remote code execution or other serious vulnerabilities

Response

Reports submitted through Private Vulnerability Reporting will be reviewed by the project maintainers. Please allow reasonable time for investigation and remediation.

Thank you for helping keep HackTogether_01 and its users secure.

There aren't any published security advisories