jjideenschmiede · gowizzard · Jul 24, 2025 · Jul 24, 2025 · Copilot · Jul 24, 2025
diff --git a/LICENSE.md b/LICENSE.md
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 J&J Ideenschmiede GmbH
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/SECURITY.md b/SECURITY.md
@@ -0,0 +1,23 @@
+# Security Policy
+
+## Supported Versions
+
+As this project serves as the backend for an application, we are committed to maintaining the security of our platform by ensuring that only the most recent release is supported with security updates. Once a new version is released, it is immediately deployed, rendering the previous version obsolete in a live environment. Therefore, we encourage all users to keep their systems up to date with the latest release to benefit from the latest security enhancements.
+
+| Version           | Supported          |
+|-------------------|--------------------|
+| Latest Release    | :white_check_mark: |
+| Previous Releases | :x:                |
+
+## Reporting a Vulnerability
+
+If you notice a security vulnerability, we encourage you to take an active role in our security process by directly creating a pull request with the necessary adjustments to address the issue. This proactive approach helps us ensure that vulnerabilities are swiftly resolved, maintaining the integrity and safety of our project.
+
+When creating a pull request to address a security vulnerability, please include:
+
+- A detailed description of the vulnerability and its potential impact.
+- A step-by-step guide to reproduce the issue, if applicable.
+- The specific changes you propose to mitigate the vulnerability.
+- Any additional information or context that might help in the assessment and resolution of the problem.
+
+This direct method of reporting and resolving security issues facilitates a more efficient and effective response, allowing us to implement security improvements with the help of our community. We appreciate your contributions to making our project more secure.
-If you notice a security vulnerability, we encourage you to take an active role in our security process by directly creating a pull request with the necessary adjustments to address the issue. This proactive approach helps us ensure that vulnerabilities are swiftly resolved, maintaining the integrity and safety of our project.
-
-When creating a pull request to address a security vulnerability, please include:
-
- A detailed description of the vulnerability and its potential impact.
- A step-by-step guide to reproduce the issue, if applicable.
- The specific changes you propose to mitigate the vulnerability.
- Any additional information or context that might help in the assessment and resolution of the problem.
-
-This direct method of reporting and resolving security issues facilitates a more efficient and effective response, allowing us to implement security improvements with the help of our community. We appreciate your contributions to making our project more secure.
+If you discover a security vulnerability, we request that you report it privately to us to ensure it can be addressed before being disclosed publicly. Please send an email to `security@company.com` with the details of the vulnerability. Alternatively, you can use GitHub's private security advisory feature to report the issue securely.
+
+When reporting a security vulnerability, please include:
+
+- A detailed description of the vulnerability and its potential impact.
+- A step-by-step guide to reproduce the issue, if applicable.
+- Any additional information or context that might help in the assessment and resolution of the problem.
+
+We are committed to addressing security issues promptly and will work with you to ensure that the vulnerability is resolved effectively. We appreciate your efforts in helping us maintain the security and integrity of our project.
-If you notice a security vulnerability, we encourage you to take an active role in our security process by directly creating a pull request with the necessary adjustments to address the issue. This proactive approach helps us ensure that vulnerabilities are swiftly resolved, maintaining the integrity and safety of our project.
-
-When creating a pull request to address a security vulnerability, please include:
-
- A detailed description of the vulnerability and its potential impact.
- A step-by-step guide to reproduce the issue, if applicable.
- The specific changes you propose to mitigate the vulnerability.
- Any additional information or context that might help in the assessment and resolution of the problem.
-
-This direct method of reporting and resolving security issues facilitates a more efficient and effective response, allowing us to implement security improvements with the help of our community. We appreciate your contributions to making our project more secure.
+If you discover a security vulnerability, we request that you report it privately to us to ensure it can be addressed before being disclosed publicly. Please send an email to `security@company.com` with the details of the vulnerability. Alternatively, you can use GitHub's private security advisory feature to report the issue securely.
+
+When reporting a security vulnerability, please include:
+
+- A detailed description of the vulnerability and its potential impact.
+- A step-by-step guide to reproduce the issue, if applicable.
+- Any additional information or context that might help in the assessment and resolution of the problem.
+
+We are committed to addressing security issues promptly and will work with you to ensure that the vulnerability is resolved effectively. We appreciate your efforts in helping us maintain the security and integrity of our project.