[Snyk] Security upgrade werkzeug from 2.2.3 to 3.1.4

[RemyLoveLogicAI]

User description

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

transformers 4.30.2 requires safetensors, which is not installed.
timm 0.9.12 requires safetensors, which is not installed.
python-docx 1.1.2 has requirement typing-extensions>=4.9.0, but you have typing-extensions 4.7.1.
paddlepaddle 1.8.5 requires scipy, which is not installed.
paddlepaddle 1.8.5 has requirement opencv-python<=4.2.0.32, but you have opencv-python 4.12.0.88.
paddleocr 2.7.5 requires scikit-image, which is not installed.
paddleocr 2.7.5 has requirement Pillow>=10.0.0, but you have Pillow 9.5.0.
paddleocr 2.7.5 has requirement opencv-python<=4.6.0.66, but you have opencv-python 4.12.0.88.
imgaug 0.4.0 requires scipy, which is not installed.
imgaug 0.4.0 requires scikit-image, which is not installed.
gradio 3.34.0 requires ffmpy, which is not installed.
easyocr 1.7.2 requires ninja, which is not installed.
easyocr 1.7.2 requires scikit-image, which is not installed.
easyocr 1.7.2 requires scipy, which is not installed.
easyocr 1.7.2 requires python-bidi, which is not installed.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.
anthropic 0.38.0 requires jiter, 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.

---

Summary by cubic

Upgraded Werkzeug from 2.2.3 to 3.1.4 to fix a security vulnerability and harden the app. Adds a pin in requirements.txt.

• Dependencies
  • Pin werkzeug>=3.1.4 (fixes SNYK-PYTHON-WERKZEUG-14151620).

^{Written for commit a8f2c17. Summary will update automatically on new commits.}

Summary by Bito

• Upgrades the Werkzeug library from version 2.2.3 to 3.1.4 to address a security vulnerability identified by Snyk.
• The change is reflected in the requirements.txt file, where the new version is pinned to ensure the application uses a secure version.
• This update is crucial for maintaining the security integrity of the project.
• Overall, the update addresses a security risk by upgrading the Werkzeug library and modifying the requirements.txt file.

---

CodeAnt-AI Description

Pin Werkzeug to a secure version to address a known vulnerability

What Changed

• Added an explicit requirement for Werkzeug 3.1.4 or newer to remove a known security vulnerability in older versions

Impact

✅ Lower risk of web endpoint compromise
✅ Fewer security vulnerability alerts in dependency scans
✅ Safer API and dashboard interactions for end users

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[safedep]

SafeDep Report Summary

Package Details

Package	Malware	Vulnerability	Risky License	Report
werkzeug @ 3.1.4 requirements.txt				🔗

_{This report is generated by SafeDep Github App}

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-62edf664b745cd6a4297496a5979f4a7

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Summary of Changes

Hello @RemyLoveLogicAI, 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 addresses a critical security vulnerability by upgrading the werkzeug package to its latest secure version. The change was automatically generated by Snyk, ensuring that the project's dependencies are up-to-date and secure against known exploits, specifically targeting a vulnerability within the werkzeug library.

Highlights

• Security Upgrade: The werkzeug dependency has been upgraded from version 2.2.3 to 3.1.4 to address a security vulnerability identified by Snyk.
• Automated Fix: This pull request was automatically generated by Snyk to apply the necessary security fix for the identified vulnerability.

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

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades werkzeug to version 3.1.4 to address a security vulnerability. While the security fix is important, the upgrade is from version 2.x to 3.x, which is a major version bump containing breaking changes. I have added a critical comment on the change in requirements.txt highlighting the risk of this direct dependency pinning and recommending a safer approach by updating the parent dependency. Additionally, I've made a medium-severity suggestion to add a missing newline at the end of the file for better compatibility. Given the existing dependency conflicts noted in the pull request description, this change should be handled with extreme care and requires thorough testing to prevent breaking the application.

[gemini-code-assist]

This change pins werkzeug to version 3.1.4 or higher to fix a security vulnerability. However, this is a major version upgrade from the previously used 2.x version, which introduces significant breaking changes. Directly pinning a transitive dependency like this, especially across a major version, is highly risky and can break your application if other dependencies rely on werkzeug 2.x (e.g., older versions of Flask).

It is strongly recommended to identify which direct dependency in your project uses werkzeug and upgrade that parent dependency to a version that uses a non-vulnerable version of werkzeug. If that's not feasible, this change requires extensive testing to ensure the application still functions correctly. The numerous dependency warnings in the PR description already indicate a fragile environment, and this change could exacerbate the issues.

[gemini-code-assist]

This file is missing a newline character at the end. It's a good practice for text files to end with one to prevent potential issues with some tools and file manipulations (e.g., cat) and to follow POSIX conventions. I've suggested adding one.

werkzeug>=3.1.4 # not directly required, pinned by Snyk to avoid a vulnerability

[cubic-dev-ai]

No issues found across 1 file