-
Notifications
You must be signed in to change notification settings - Fork 70
LCORE-1108: Updated Konflux dependencies #1090
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
Merged
tisnik
merged 1 commit into
lightspeed-core:main
from
tisnik:lcore-1108-updated-dependencies-konflux
Feb 2, 2026
+62
−56
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🧩 Analysis chain
🏁 Script executed:
git ls-files | head -20Repository: lightspeed-core/lightspeed-stack
Length of output: 782
🏁 Script executed:
Repository: lightspeed-core/lightspeed-stack
Length of output: 239
🏁 Script executed:
Repository: lightspeed-core/lightspeed-stack
Length of output: 358
🏁 Script executed:
Repository: lightspeed-core/lightspeed-stack
Length of output: 4043
🏁 Script executed:
# Also check the beginning to see the file structure head -30 requirements.hashes.source.txtRepository: lightspeed-core/lightspeed-stack
Length of output: 1919
🏁 Script executed:
# Read pyproject.toml to check dependencies as per the learning cat pyproject.tomlRepository: lightspeed-core/lightspeed-stack
Length of output: 6008
🏁 Script executed:
Repository: lightspeed-core/lightspeed-stack
Length of output: 600
🌐 Web query:
security vulnerabilities cachetools 7.0.0 CVE💡 Result:
cachetools(the project’s current releases are in the 6.x line; PyPI shows recent 6.2.x releases, e.g., 6.2.6). [1]cachetoolsin major vulnerability trackers (e.g., Safety DB and Snyk both report no known security issues forcachetools). [2] [3]If you meant
CacheToolsUtils(a different PyPI project that does have a 7.0 series), say so and I’ll check CVEs/advisories for that package/version specifically. [4]Sources: [1] [2] [3] [4]
🌐 Web query:
security vulnerabilities litellm 1.81.6 CVE💡 Result:
No public CVE records I found list LiteLLM 1.81.6 as affected. The published LiteLLM CVEs (so far) are scoped to older versions (either specific versions or “before” / “up to” ranges) that are well below 1.81.6, e.g.:
If you want, paste your deployment mode (Python library vs proxy server) and enabled endpoints, and I can map which of the above are relevant attack-surface-wise even if your version is newer.
Sources: [1] [2] [3] [4] [5] [6] [7]
🌐 Web query:
security vulnerabilities protobuf 6.33.5 CVE💡 Result:
protobuf6.33.5 (PyPI) is primarily relevant because it fixes the most recent protobuf Python CVE:google.protobuf.json_format.ParseDict()with nestedAny)Affects protobuf ≤ 6.33.4; upgrading to 6.33.5 removes exposure. The CVE description is in NVD. [1][2][3]
Other notable recent protobuf-python CVE (already fixed well before 6.33.5):
Patched in 6.31.1 (and also 4.25.8 / 5.29.5), so 6.33.5 is not affected. [4]
As of the sources above, there are no additional CVEs specifically reported as affecting protobuf 6.33.5 (it appears as a “fixed/upgrade-to” version for the active recursion-related issue). [2][3]
Sources
[1] NVD – CVE-2026-0994: https://nvd.nist.gov/vuln/detail/CVE-2026-0994
[2] Snyk (protobuf PyPI vuln page showing fix version): https://security.snyk.io/package/pip/protobuf/5.29.0
[3] Resolved Security (affected ≤6.33.4): https://www.resolvedsecurity.com/vulnerability-catalog/CVE-2026-0994
[4] GitHub Security Advisory (GHSA-8qvm-5x2c-j2w7 / CVE-2025-4565): GHSA-8qvm-5x2c-j2w7
🌐 Web query:
security vulnerabilities psutil 7.2.2 CVE💡 Result:
As of Feb 2, 2026, there are no publicly listed CVEs known to affect
psutil7.2.2.psutil7.2.2 was uploaded to PyPI on Jan 28, 2026. [1]psutilhas historical vulnerabilities, they do not affect 7.2.2. [2]Sources: [1] PyPI release files for psutil 7.2.2, [2] Snyk psutil package page, [3] NVD entry for CVE-2019-18874.
🌐 Web query:
security vulnerabilities pyjwt 2.11.0 CVE💡 Result:
As of February 2, 2026, I can’t find any CVE that lists PyJWT 2.11.0 as an affected version. The public CVEs associated with PyJWT in recent years are tied to earlier versions:
iss) validation partial-match bug; affected: 2.10.0 only, fixed: 2.10.1. PyJWT 2.11.0 is not affected. [1]Bottom line: No CVE I found currently implicates PyJWT 2.11.0; the main actionable items are “don’t use 2.10.0” (due to CVE-2024-53861) and ensure your application explicitly restricts accepted algorithms when decoding tokens (the core risk described in CVE-2022-29217). [1][2]
Sources: NVD CVE entries and distro trackers. [1][2][3][4]
🏁 Script executed:
Repository: lightspeed-core/lightspeed-stack
Length of output: 58
🌐 Web query:
cachetools latest version PyPI 2026💡 Result:
The latest cachetools release on PyPI is 6.2.6, uploaded January 27, 2026. [1]
Critical:
cachetools==7.0.0does not exist on PyPI.The version specified in the requirements file is invalid. The latest
cachetoolsrelease is 6.2.6 (released January 27, 2026). Version 7.0.0 does not exist in any release on PyPI. This will cause installation failures.Update the
cachetoolsentry to use a valid version from the 6.x series (e.g.,6.2.6or6.2.0). Review all dependencies in the file to ensure they reference actual released versions on PyPI.The other dependency versions checked (litellm 1.81.6, protobuf 6.33.5, psutil 7.2.2, pyjwt 2.11.0, and others) show no known security advisories.
🤖 Prompt for AI Agents