[Snyk] Fix for 2 vulnerabilities

[q1blue]

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

Snyk changed the following file(s):

• requirements-ci.txt

⚠️ Warning

moto 2.1.0 requires werkzeug, which is not installed.
flake8 4.0.1 has requirement importlib-metadata<4.3; python_version < "3.8", but you have importlib-metadata 6.7.0.
buildbot 4.3.0 requires autobahn, which is not installed.
buildbot 4.3.0 has requirement unidiff>=0.7.5, but you have unidiff 0.7.3.

---

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:

🦉 Allocation of Resources Without Limits or Throttling

---

Important

Upgrade sqlparse and Werkzeug in requirements-ci.txt to fix vulnerabilities.

• Dependencies:
  • Upgrade sqlparse from 0.4.2 to 0.5.4 in requirements-ci.txt to fix vulnerability SNYK-PYTHON-SQLPARSE-14157217.
  • Upgrade Werkzeug from 2.1.2 to 3.1.4 in requirements-ci.txt to fix vulnerability SNYK-PYTHON-WERKZEUG-14151620.

^{This description was created by for aeaec65. You can customize this summary. It will automatically update as commits are pushed.}

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
buildbot	Error			Dec 4, 2025 10:05am
csb-b6x6kw	Ready	Preview	Comment	Dec 4, 2025 10:05am

[changeset-bot]

⚠️ No Changeset found

Latest commit: aeaec65

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to aeaec65 in 47 seconds. Click for details.

• Reviewed 22 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. requirements-ci.txt:96

• Draft comment:
  Upgrade sqlparse to 0.5.4 to address the vulnerability. Ensure no breaking API changes affect SQL parsing logic.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is related to a dependency change, specifically upgrading sqlparse to a new version. It also asks the author to ensure that there are no breaking API changes affecting SQL parsing logic. This falls under the rule of not asking the author to ensure behavior is intended or tested, and it involves a dependency change.

2. requirements-ci.txt:111

• Draft comment:
  Update Werkzeug to 3.1.4 to fix the known vulnerability. Verify compatibility with your app’s usage since there may be breaking changes.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is about updating a dependency, Werkzeug, to a specific version to fix a vulnerability. It also advises verifying compatibility due to potential breaking changes. This falls under the rule of not commenting on dependency changes or asking the author to verify compatibility, which is not allowed.

Workflow ID: wflow_2sDRqt0rE9ep9R8t

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}