[Snyk] Fix for 23 vulnerabilities

[robertatakenaka]

Snyk has created this PR to fix 23 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements/base.txt

⚠️ Warning

celery 5.3.0 requires kombu, which is not installed.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Improper Output Neutralization for Logs
🦉 SQL Injection
🦉 More lessons are available in Snyk Learn

[Copilot]

Pull request overview

This PR, generated by Snyk, updates Python dependencies to remediate reported vulnerabilities by adding explicit minimum versions for transitive packages.

Changes:

• Normalizes the pycountry entry formatting in requirements/base.txt.
• Adds explicit dependency floors for sqlparse and zipp to address vulnerability findings.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

requirements/base.txt pins nearly all dependencies with ==, but these new entries use >=. This makes installs non-reproducible and can cause unexpected upgrades. Consider pinning sqlparse and zipp to specific patched versions (or moving them into a dedicated constraints/overrides mechanism if that’s how this repo handles transitive security pins).

Suggested change

	sqlparse>=0.5.4 # not directly required, pinned by Snyk to avoid a vulnerability
	zipp>=3.19.1 # not directly required, pinned by Snyk to avoid a vulnerability
	sqlparse==0.5.4 # not directly required, pinned by Snyk to avoid a vulnerability
	zipp==3.19.1 # not directly required, pinned by Snyk to avoid a vulnerability

[Copilot]

PR description/metadata says this fix upgrades django (3.2.25 → 4.2.27), but requirements/base.txt currently pins django==5.2.10 and this PR doesn’t change it. Please confirm the Snyk report/PR description matches the actual dependency state so reviewers can validate the intended remediation.