[Snyk] Fix for 6 vulnerabilities

[gmuraru]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements.dev.txt

⚠️ Warning

safety 2.3.5 has requirement packaging<22.0,>=21.0, but you have packaging 23.2.
mypy 0.790 has requirement typed-ast<1.5.0,>=1.4.0, but you have typed-ast 1.5.5.
mypy 0.790 has requirement mypy-extensions<0.5.0,>=0.4.3, but you have mypy-extensions 1.0.0.
ipykernel 5.5.0 requires ipython, which is not installed.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	531/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 4.2	Remote Code Execution (RCE) SNYK-PYTHON-IPYTHON-3318382	ipython: 7.34.0 -> 8.10.0	No	Proof of Concept
	589/1000 Why? Has a fix available, CVSS 7.5	Information Exposure SNYK-PYTHON-NOTEBOOK-2441824	notebook: 6.4.1 -> 6.4.12	No	No Known Exploit
	449/1000 Why? Has a fix available, CVSS 4.7	Access Restriction Bypass SNYK-PYTHON-NOTEBOOK-2928995	notebook: 6.4.1 -> 6.4.12	No	No Known Exploit
	509/1000 Why? Has a fix available, CVSS 5.9	Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-SETUPTOOLS-3180412	setuptools: 39.0.1 -> 65.5.1	No	No Known Exploit
	384/1000 Why? Has a fix available, CVSS 3.4	Open Redirect SNYK-PYTHON-TORNADO-5537286	tornado: 6.2 -> 6.3.3	No	No Known Exploit
	494/1000 Why? Has a fix available, CVSS 5.6	HTTP Request Smuggling SNYK-PYTHON-TORNADO-5840803	tornado: 6.2 -> 6.3.3	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

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.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Remote Code Execution (RCE)
🦉 Information Exposure
🦉 Access Restriction Bypass
🦉 More lessons are available in Snyk Learn