Add comprehensive security and contribution documentation

Co-authored-by: christianlouis <361235+christianlouis@users.noreply.github.com>
2026-02-06 22:00:17 +00:00
parent 53f20f25d1
commit 9ae57b2a8f
14 changed files with 2417 additions and 1 deletions
@@ -0,0 +1,58 @@
+---
+name: Security Vulnerability
+about: Report a security issue (CONFIDENTIAL)
+title: '[SECURITY] '
+labels: 'security'
+assignees: ''
+---
+
+⚠️ **IMPORTANT: Do not create a public issue for serious security vulnerabilities**
+
+For serious security vulnerabilities, please email the maintainers directly instead of creating a public issue. See [SECURITY.md](../../SECURITY.md) for contact information.
+
+---
+
+## Security Issue Type
+- [ ] Authentication/Authorization issue
+- [ ] Data exposure
+- [ ] Injection vulnerability (SQL, XSS, etc.)
+- [ ] Cryptography issue
+- [ ] Dependency vulnerability
+- [ ] Configuration security
+- [ ] Other: _____
+
+## Affected Component
+- [ ] Backend API
+- [ ] Frontend/UI
+- [ ] Database
+- [ ] Docker configuration
+- [ ] Documentation
+- [ ] Dependencies
+
+## Severity Assessment
+- [ ] Critical (immediate action required)
+- [ ] High (significant risk)
+- [ ] Medium (moderate risk)
+- [ ] Low (minor risk)
+
+## Description
+Describe the security issue in detail.
+
+## Impact
+What is the potential impact of this vulnerability?
+
+## Steps to Reproduce
+Provide steps to reproduce the vulnerability.
+
+## Affected Versions
+Which versions of DMARQ are affected?
+
+## Suggested Remediation
+If you have suggestions for fixing the issue, provide them here.
+
+## References
+Links to similar vulnerabilities, CVEs, or relevant documentation.
+
+---
+
+**Remember**: For critical vulnerabilities, use private disclosure via email instead of public issues.