[Snyk] Security upgrade jupyter-server from 1.24.0 to 2.11.2 #206
Conversation
The following vulnerabilities are fixed by pinning transitive dependencies: - https://snyk.io/vuln/SNYK-PYTHON-JUPYTERSERVER-6099119
![codescene-delta-analysis[bot]](/https://avatars.githubusercontent.com/in/53921?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Code Health Quality Gates: OK
- Declining Code Health: 0 findings(s) 🚩
- Improving Code Health: 0 findings(s) ✅
- Affected Hotspots: 0 files(s) 🔥
Recommended Review Level: Inconclusive -- All modified content is filtered away. This is either due to excluded content in your CodeScene settings, or because the change set only contains renames.
View detailed results in CodeScene
for more information, see https://pre-commit.ci
There was a problem hiding this comment.
✅ Code Health Quality Gates: OK
- Declining Code Health: 0 findings(s) 🚩
- Improving Code Health: 0 findings(s) ✅
- Affected Hotspots: 0 files(s) 🔥
Recommended Review Level: Inconclusive -- All modified content is filtered away. This is either due to excluded content in your CodeScene settings, or because the change set only contains renames.
View detailed results in CodeScene
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #206 +/- ##
=======================================
Coverage 96.58% 96.58%
=======================================
Files 56 56
Lines 3956 3956
=======================================
Hits 3821 3821
Misses 135 135 ☔ View full report in Codecov by Sentry. |
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
Vulnerabilities that will be fixed
By pinning:
Why? Recently disclosed, Has a fix available, CVSS 3.5
SNYK-PYTHON-JUPYTERSERVER-6099119
jupyter-server:1.24.0 -> 2.11.2(*) Note that the real score may have changed since the PR was raised.
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.
Check the changes in this PR to ensure they won't cause issues with your project.
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
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Generation of Error Message Containing Sensitive Information