The security of the Lunch Booking System is a top priority. We appreciate the efforts of security researchers and the community to help us maintain a secure and reliable application.
If you discover a security vulnerability, please report it to us privately. Do not disclose the vulnerability publicly until it has been addressed.
To report a vulnerability, please use GitHub's private vulnerability reporting feature.
When reporting a vulnerability, please provide the following information:
- A detailed description of the vulnerability, including the steps to reproduce it.
- The version of the application you are using.
- Any relevant logs or screenshots.
We will do our best to respond to your report within 48 hours.
The following table shows which versions of the Lunch Booking System are currently being supported with security updates:
| Version | Supported |
|---|---|
1.x |
✅ |
< 1.0 |
❌ |
We strive to follow security best practices throughout the development lifecycle. This includes:
- Code Reviews: All code is reviewed for security vulnerabilities before it is merged into the
masterbranch. - Dependency Scanning: We use GitHub's dependency scanning to identify and patch vulnerable dependencies.
- Static Analysis: We use CodeQL to perform static analysis of our codebase to identify potential security vulnerabilities.
- Container Scanning: We scan our Docker images for vulnerabilities before they are pushed to our container registries.
We appreciate your help in keeping the Lunch Booking System secure.