text: Title: Review the GlobaLeaks codebase for Best Practices and Consistency
  Body: ## Description:
  Globaleaks is a collaborative open-source project that welcomes contributions from developers worldwide. One important aspect of maintaining a healthy codebase is regular code reviews. As a new contributor, you will have the opportunity to help by reviewing the code in recent pull requests (PRs) for best practices, consistency, and potential improvements.
  
  You will also have the option to propose improvements to the code by submitting your own pull request. This is a great way to become more familiar with the project and ensure the code remains clean, efficient, and maintainable.
  
  ## Steps:
  1. **Explore Open Pull Requests:**
     - Access the [pull requests](https://github.com/globaleaks/globaleaks-whistleblowing-software/pulls) or directly to the [codebase](https://github.com/globaleaks/globaleaks-whistleblowing-software).
     - Browse through the open pull requests or the codebase to find something that interests you. In case of a pull request look for one that is ready for review, i.e., it has been submitted and is awaiting approval.
  
  2. **Perform the Code Review:**
     - Thoroughly review the code in the pull request, checking for the following:
       - **Adherence to coding standards:** Make sure the code follows the style guide (e.g., naming conventions, indentation).
       - **Code quality:** Ensure the code is clean, understandable, and efficient.
       - **Functionality:** Confirm that the code works as expected and doesn’t break existing functionality.
       - **Security concerns:** Look for potential security issues, such as SQL injection, XSS vulnerabilities, etc.
       - **Documentation:** Check if there are any missing comments or documentation in the code.
  
  3. **Leave Constructive Feedback:**
     - If you notice anything that could be improved, leave clear, constructive feedback in the comments section of the pull request.
     - Point out any areas where the code can be optimized or made more readable. If something is unclear, ask for clarification.
  
  4. **Suggest Changes or Improvements:**
     - If you find something that needs to be changed or fixed, suggest improvements directly in the PR or propose your own changes by submitting a new pull request.
     - You can fork the repository, make your changes, and create a new PR that addresses the issues you identified.
  
  5. **Approve or Request Changes:**
     - If everything looks good and you’re satisfied with the pull request, you can approve it.
     - If you feel that changes are needed, request the author to make those changes and provide guidance on what should be done.
  
  6. **Submit a Pull Request (Optional):**
     - If you make any changes or improvements (e.g., fixes or optimizations), create a **pull request** with your changes.
     - Make sure your pull request is based on the most recent version of the code to avoid conflicts.
  
  ## Prerequisites:
  - **Knowledge of Git and GitHub:** Basic understanding of how to clone repositories, create branches, and submit pull requests.
  - **Familiarity with the Globaleaks Codebase:** You don’t need to be an expert, but a general understanding of how Globaleaks is structured and its core components will help.
  - **Experience with Code Reviews (Optional):** If you have experience reviewing code, this will be a great opportunity to practice and improve your skills.
  
  ## Why it's a Good First Issue:
  - Reviewing pull requests and proposing changes is an excellent way to get familiar with the Globaleaks codebase.
  - You’ll learn best practices for code quality, security, and maintainability while contributing to the project’s success.
  - This task encourages collaboration and helps ensure that the codebase remains clean and efficient for all contributors.
  - If you prefer, you can explore the codebase independently and contribute your own improvements.
  
  ## Helpful Links:
  - [Globaleaks GitHub Repository](https://github.com/globaleaks/globaleaks-whistleblowing-software)
  - [GitHub Pull Request Workflow](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests)