[Snyk] Security upgrade urllib3 from 2.0.7 to 2.5.0

[henols]

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

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

equests 2.31.0 requires urllib3, 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:

🦉 Open Redirect

[gemini-code-assist]

Summary of Changes

Hello @henols, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request is an automated security fix initiated by Snyk. Its primary purpose is to enhance the project's security posture by upgrading a critical underlying dependency, urllib3, to a version that mitigates known vulnerabilities.

Highlights

• Security Upgrade: This pull request, automatically generated by Snyk, upgrades the urllib3 dependency from version 2.0.7 to 2.5.0 to address two identified security vulnerabilities.
• Dependency Pinning: The requirements.txt file is updated to explicitly pin urllib3 to version 2.5.0. A comment indicates this is a security measure, even if urllib3 is not a direct requirement.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades urllib3 to version 2.5.0 or newer to patch security vulnerabilities. While the upgrade is necessary, I've identified a potential dependency conflict with the requests library that could break builds. I've suggested adding a comment to requirements.txt to make this implicit dependency requirement explicit. I also noted that the project's dependency management could be improved by consolidating dependencies into a single file (pyproject.toml) to ensure consistency.

[gemini-code-assist]

While this change is important for security, directly pinning a transitive dependency like urllib3 can create dependency conflicts.

The requests library, a direct dependency of your project, has specific version constraints for urllib3:

• requests < 2.32.0 (e.g., 2.31.0) requires urllib3 < 2.1, making it incompatible with this change.
• requests >= 2.32.0 is compatible with urllib3 >= 2.5.0.

This means that for this upgrade to work correctly, requests must also be at version 2.32.0 or newer. Without an explicit constraint on requests, pip might fail to resolve dependencies, especially in environments with an older requests version.

To make this requirement clear and prevent future build issues, I suggest adding a note to the comment.

On a related note, I see dependencies are managed in both requirements.txt and pyproject.toml. For better maintainability, consider consolidating them into pyproject.toml as the single source of truth.

urllib3>=2.5.0 # not directly required, pinned by Snyk to avoid a vulnerability; requires requests>=2.32.0