|
| 1 | +# LibrisAPI Security Policy |
| 2 | + |
| 3 | +At LibrisAPI, we are committed to maintaining the highest level of security for our users' data. This document outlines our security policies and how to report security vulnerabilities. |
| 4 | + |
| 5 | +## Supported Versions |
| 6 | + |
| 7 | +| Version | Support Status | |
| 8 | +| ------- | -------------- | |
| 9 | +| 1.x | Supported | |
| 10 | +| < 1.0 | Not Supported | |
| 11 | + |
| 12 | +Security updates will only be applied to supported versions. |
| 13 | + |
| 14 | +## Reporting Security Vulnerabilities |
| 15 | + |
| 16 | +If you discover a security vulnerability in LibrisAPI, please report it to us by following these steps: |
| 17 | + |
| 18 | +1. **Description:** Prepare a detailed report that includes a description of the vulnerability, how to reproduce it, and the potential impact. |
| 19 | +2. **Contact:** Send your report via email to [core@necoti.dev](mailto:core@necoti.dev). Please encrypt your email (e.g., using GPG) and include your public key. |
| 20 | +3. **Confidentiality:** Avoid disclosing the vulnerability publicly. After contacting us, we will work together to resolve the issue and release the necessary updates. |
| 21 | + |
| 22 | +## Security Measures |
| 23 | + |
| 24 | +The following security measures are implemented in LibrisAPI: |
| 25 | + |
| 26 | +* **Password Hashing:** User passwords are securely hashed using bcryptjs. |
| 27 | +* **JWT (JSON Web Token) Authentication:** Authentication is performed securely using JWT. |
| 28 | +* **Input Validation:** User inputs are validated to prevent potential security vulnerabilities. |
| 29 | +* **HTTPS Usage:** Communication between the API and users is encrypted using the HTTPS protocol. |
| 30 | +* **Dependency Updates:** All dependencies used in the project are regularly updated to patch security vulnerabilities. |
| 31 | +* **Rate Limiting:** Request rates are limited to prevent abuse of the API. |
| 32 | + |
| 33 | +## Disclaimer |
| 34 | + |
| 35 | +LibrisAPI is provided "as is" and without any warranty. We are not responsible for any security breaches or data loss resulting from the use of this project. |
| 36 | + |
| 37 | +## Contact |
| 38 | + |
| 39 | +If you have any security-related questions or concerns, please contact us at [core@necoti.dev](mailto:core@necoti.dev). |
| 40 | + |
| 41 | +This core policy is continuously updated to ensure the core of LibrisAPI. Please check back regularly. |
0 commit comments