[Snyk] Fix for 5 vulnerabilities

[jbampton]

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

Snyk changed the following file(s):

• doc/requirements-docs.txt

⚠️ Warning

sphinx 5.3.0 requires requests, which is not installed.
sphinx 5.3.0 has requirement docutils<0.20,>=0.14, but you have docutils 0.20.1.
myst-parser 1.0.0 has requirement docutils<0.20,>=0.15, but you have docutils 0.20.1.

---

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.

---

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Open Redirect

[gemini-code-assist]

Summary of Changes

Hello @jbampton, 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, automatically generated by Snyk, addresses five security vulnerabilities detected in the project's pip dependencies. It updates several key packages to their latest secure versions, thereby enhancing the overall security posture of the application by mitigating known risks.

Highlights

• Dependency Updates: Upgraded tornado to 6.3.2, setuptools to 65.5.1, zipp to 3.19.1, urllib3 to 1.26.19, and requests to 2.32.2 to address identified security vulnerabilities.
• Automated Fix: This pull request was automatically generated by Snyk to remediate 5 security vulnerabilities found in the project's pip dependencies.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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. ↩

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	tornado@​6.5.2
	setuptools@​80.9.0
	urllib3@​2.6.1
	requests@​2.32.5
	zipp@​3.23.0

View full report

[gemini-code-assist]

Code Review

This pull request from Snyk addresses several security vulnerabilities by updating dependencies. While these updates are important, the PR description itself highlights a critical dependency conflict that is not fully addressed. The docutils package has an incompatible version (0.20.1) for sphinx and myst-parser, which require a version <0.20. This will likely cause the documentation build to fail. It is highly recommended to also pin docutils to a compatible version (e.g., docutils<0.20) in doc/requirements-docs.txt to ensure the project remains buildable. Additionally, I've left a comment suggesting to sort the newly added dependencies for better maintainability.

[gemini-code-assist]

For better maintainability and consistency with the rest of the file, it's good practice to keep dependencies sorted alphabetically. Please sort the newly added packages.

requests>=2.32.2 # not directly required, pinned by Snyk to avoid a vulnerability
setuptools>=65.5.1 # not directly required, pinned by Snyk to avoid a vulnerability
tornado>=6.3.2 # not directly required, pinned by Snyk to avoid a vulnerability
urllib3>=1.26.19 # not directly required, pinned by Snyk to avoid a vulnerability
zipp>=3.19.1 # not directly required, pinned by Snyk to avoid a vulnerability

[jbampton]

https://64-shades--315.org.readthedocs.build/en/315/