Skip to content

Security: tjklint/tjklint.github.io

Security

.github/SECURITY.md

Security Policy

Reporting a Vulnerability

If you discover a security vulnerability, please report it responsibly. We appreciate your help in keeping our project secure for everyone.

To report a vulnerability:

  1. Do not open a public issue. Instead, contact us directly by email at timothyjklint [AT] gmail [DOT] com.
  2. Include as much information as possible, including:
    • A description of the vulnerability.
    • Steps to reproduce it.
    • Any potential impact on the project.
  3. We will acknowledge receipt within 48 hours and work to validate and address the vulnerability as soon as possible.

Responsible Disclosure

We kindly ask that you follow responsible disclosure practices and give us time to investigate and resolve the issue before publicly disclosing any vulnerabilities.

Security Best Practices for Contributors

If you're contributing to this project, here are a few guidelines to help keep the codebase secure:

  1. Avoid Hard-Coded Secrets: Do not include API keys, passwords, or other secrets directly in the code.
  2. Use Secure Coding Practices: Follow basic secure coding practices, such as input validation and error handling.
  3. Update Dependencies: Make sure any dependencies are up-to-date and free from known vulnerabilities.

Thank you for helping us maintain a secure project!

There aren’t any published security advisories