[Snyk] Security upgrade pillow from 9.5.0 to 10.0.1

[gitworkflows]

User description

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

Snyk changed the following file(s):

• examples/speed_estimation/requirements.txt

⚠️ Warning

data-gradients 0.3.2 requires scipy, which is not installed.
scikit-learn 1.0.2 requires scipy, which is not installed.
super-gradients 3.5.0 requires scipy, which is not installed.
xhtml2pdf 0.2.11 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.
onnxruntime 1.13.1 has requirement numpy>=1.21.6, but you have numpy 1.21.3.
pyhanko 0.20.1 has requirement pyhanko-certvalidator==0.24.*, but you have pyhanko-certvalidator 0.26.5.
sphinx-rtd-theme 2.0.0 has requirement sphinx<8,>=5, but you have sphinx 4.0.3.
tensorboard 2.11.2 has requirement setuptools>=41.0.0, but you have setuptools 40.5.0.

---

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.

---

PR Type

enhancement, dependencies

---

Description

• Updated the examples/speed_estimation/requirements.txt file to pin the pillow package to version 10.0.1 or higher, addressing a known security vulnerability.
• This change was made to reduce vulnerabilities in the project's dependencies as identified by Snyk.

---

Changes walkthrough 📝

	Relevant files
Dependencies	requirements.txt Pin `pillow` dependency to mitigate security vulnerability examples/speed_estimation/requirements.txt Added a version constraint for the pillow package. Pinned pillow to version 10.0.1 or higher to address a security vulnerability. +1/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR is a security update that upgrades the Pillow package from version 9.5.0 to 10.0.1 to address a known vulnerability (SNYK-PYTHON-PILLOW-5918878). The change is implemented by adding a pinned version requirement in the requirements.txt file.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added a pinned version requirement for Pillow package to address security vulnerability	Added explicit version constraint for Pillow package (>=10.0.1) Added comment explaining the requirement was added by Snyk for security	examples/speed_estimation/requirements.txt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

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

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Dependency Conflicts The PR introduces a new pillow version requirement that may conflict with other dependencies. Review the warning messages about missing and conflicting dependencies to ensure compatibility.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
General	Add an upper bound version constraint to prevent future compatibility issues Consider adding an upper bound version constraint for pillow to prevent potential breaking changes in future releases. Use the syntax pillow>=10.0.1,<11.0.0. examples/speed_estimation/requirements.txt [7] -pillow>=10.0.1 # not directly required, pinned by Snyk to avoid a vulnerability +pillow>=10.0.1,<11.0.0 # not directly required, pinned by Snyk to avoid a vulnerability Apply this suggestion Suggestion importance[1-10]: 7 Why: Adding an upper version bound is a good practice to prevent potential breaking changes from major version updates, helping maintain project stability and predictability.	7

💡 Need additional feedback ? start a PR chat

[gitworkflows]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)