Skip to content

Security: RubberDuckCrew/gitdone-test

Security

.github/SECURITY.md

πŸ” Security Policy

Last Updated: April 10, 2025

πŸ“£ Reporting a Vulnerability

If you believe you've found a security vulnerability in this project, please report it privately using GitHub's security advisory feature.

πŸ“ To report:

  1. Go to the repository's "Security" tab.

  2. Click on "Report a vulnerability".

Please include the following information in your report to help us quickly assess and respond:

  • Description of the vulnerability
  • Steps to reproduce the issue
  • Expected vs. actual behavior
  • Potential impact or severity
  • Any relevant code snippets, stack traces, or logs
  • If possible, a proof of concept (PoC)

πŸ”’ Security Best Practices

We follow security-focused development practices, including:

  • Regular review and updating of dependencies
  • Avoiding hardcoded secrets or credentials
  • Code reviews for all contributions
  • Minimal required permissions for APIs and services

🀝 Responsible Disclosure

We value the security community and appreciate responsible disclosures. If you report a valid issue:

  • We will work with you to resolve it promptly
  • You can choose to remain anonymous or be credited
  • We'll keep you updated throughout the resolution process

There aren’t any published security advisories