[Snyk] Security upgrade werkzeug from 1.0.1 to 3.1.5

[ashmuck]

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

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

tensorboard 2.4.1 requires werkzeug, which is not installed.
tensorboard 2.4.1 has requirement setuptools>=41.0.0, but you have setuptools 40.5.0.
scikit-learn 1.0.2 requires scipy, 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

Note

Security dependency upgrade

• Updates Werkzeug in requirements.txt from 1.0.1 to 3.1.5.

^{Written by Cursor Bugbot for commit 345a419. This will update automatically on new commits. Configure here.}

[cursor]

Werkzeug 3.x incompatible with tensorboard 2.4.1

Medium Severity

Upgrading Werkzeug from 1.0.1 to 3.1.5 introduces a dependency incompatibility with tensorboard==2.4.1. TensorBoard 2.4.1 (from early 2021) uses internal werkzeug APIs that were removed in werkzeug 2.x/3.x, causing ImportError exceptions (e.g., cannot import name '_plain_int' from 'werkzeug._internal') when running the TensorBoard web server. The codebase uses SummaryWriter for logging training metrics, and while log writing may still work, users attempting to view metrics via tensorboard command will encounter runtime failures. Either tensorboard needs to be upgraded alongside werkzeug, or werkzeug's version constraint needs adjustment.