Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Fix for 2 vulnerabilities #13322

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented Sep 18, 2024

snyk-top-banner

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

Snyk changed the following file(s):

  • requirements.txt

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 Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Updated dependencies to enhance security and performance. 🔒🚀

📊 Key Changes

  • Upgraded tqdm from version 4.64.0 to 4.66.3.
  • Added zipp>=3.19.1 to requirements.

🎯 Purpose & Impact

  • Security: Addressed known vulnerabilities by pinning zipp version.
  • Performance: Improved progress bar utility with tqdm update, enhancing user experience.

@UltralyticsAssistant UltralyticsAssistant added the dependencies Pull requests that update a dependency file label Sep 18, 2024
@UltralyticsAssistant
Copy link
Member

👋 Hello @glenn-jocher, thank you for submitting a pull request to the ultralytics/yolov5 repository! 🚀 We're appreciative of your efforts to address vulnerabilities. Here's a quick checklist to ensure everything is on track:

  • Define a Purpose: Please make sure your PR description clearly outlines the purpose of the updates and links to any relevant issues associated with these changes.
  • Synchronize with Main: Ensure your branch is up-to-date with main. If there are any conflicts, you can resolve them by pulling the latest changes.
  • CI Checks: Verify that all CI checks are passing. If there are any failures, let's address them.
  • Documentation: If these changes impact any user-facing features, please update the documentation as needed.
  • Add Tests: Confirm that all tests are updated and passing, covering the new changes.
  • Sign the CLA: Don’t forget to sign our Contributor License Agreement if this is your first PR.

For any complex changes, a minimum reproducible example (MRE) can help us understand the context better. This response is automated, but rest assured that an Ultralytics engineer will review your PR soon and assist further. Feel free to reach out with questions or comments.

Thank you for contributing to Ultralytics! 🌟🔧

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants