docs: replace email addresses with GitHub issue links

- Remove all @example.com email addresses from documentation - Replace [email protected] with GitHub security issue links - Replace [email protected] with GitHub issue link - Update CONTRIBUTING.md to use GitHub issues instead of email - Ensure all communication happens through GitHub's issue tracking system - Avoid direct email communication for better transparency and tracking
2025-07-24 21:28:44 +02:00
parent 35e360dcf7
commit 0c989ce086
4 changed files with 15 additions and 12 deletions
@@ -15,11 +15,14 @@ We take the security of PicPeak seriously. If you have discovered a security vul

 ### 1. **Do NOT create a public GitHub issue**

-### 2. Email us at [email protected] with:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
+### 2. Report the vulnerability by:
+- Opening a [security issue](https://github.com/the-luap/picpeak/issues/new?labels=security) on GitHub
+- Mark it clearly as "SECURITY" in the title
+- Include:
+  - Description of the vulnerability
+  - Steps to reproduce
+  - Potential impact
+  - Suggested fix (if any)

 ### 3. You can expect:
 - Acknowledgment within 48 hours
@@ -79,7 +82,7 @@ We believe in responsible disclosure. Once a vulnerability is fixed:

 ## Contact

- Security issues: security@example.com
- General support: https://github.com/the-luap/picpeak/issues
+- Security issues: [Create a security issue](https://github.com/the-luap/picpeak/issues/new?labels=security) on GitHub
+- General support: [GitHub Issues](https://github.com/the-luap/picpeak/issues)

 Thank you for helping keep PicPeak and its users safe!