-
Notifications
You must be signed in to change notification settings - Fork 0
[Snyk] Fix for 2 vulnerabilities #723
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,3 +6,5 @@ ftfy | |
| tensorboard | ||
| Jinja2 | ||
| peft==0.7.0 | ||
| protobuf>=5.29.6 # not directly required, pinned by Snyk to avoid a vulnerability | ||
| zipp>=3.19.1 # not directly required, pinned by Snyk to avoid a vulnerability | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Similar to |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pinning the
protobufversion directly to>5.xcan lead to dependency conflicts.tensorboard, a direct dependency in this file, has strict version requirements forprotobuf. For instance,tensorboardversions older than2.17.0are generally not compatible withprotobuf>=5.0. This change will likely force a major version upgrade oftensorboard, which could introduce breaking changes to your project.A more robust approach is to manage your direct dependencies. Consider pinning
tensorboardon line 6 to a version that is compatible with a secureprotobufversion (e.g.,tensorboard>=2.17.0). This would allowpipto resolve a secure and compatible version ofprotobufautomatically, making your dependencies more explicit and less brittle.