Use this section to tell people about which versions of your project are currently being supported with security updates.
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| 0.9.x | ✅ |
| < 0.9 | ❌ |
We take the security of our project seriously. If you believe you've found a security vulnerability, please follow these steps to report it:
- Do NOT disclose the vulnerability publicly
- Email us at security@example.com with details about the vulnerability
- Include the following information in your report:
- Type of vulnerability
- Full path of source file(s) related to the vulnerability
- Location of affected code (line number(s))
- Proof of concept or exploit code (if possible)
- Impact of the vulnerability
- We will acknowledge receipt of your vulnerability report within 48 hours
- We will provide a more detailed response within 7 days
- We will work with you to understand and address the vulnerability
- We will keep you informed of our progress towards a fix and announcement
- We may ask for additional information or guidance
Our project follows these security practices:
- Regular dependency updates and audits
- Automated security scanning in CI/CD pipeline
- Code review process that includes security considerations
- Regular security testing and assessments
For optimal security when deploying this application, follow these guidelines:
- Always use HTTPS in production environments
- Configure proper authentication for all API endpoints
- Implement rate limiting to prevent abuse
- Keep all dependencies up-to-date
- Follow the least privilege principle for service accounts
We would like to thank the following individuals who have helped improve our security through responsible disclosure:
- (Your project can acknowledge security researchers here)
If you have responsibly disclosed a security vulnerability to us, we would be happy to acknowledge your contribution.