Open snyk-bot opened 2 years ago
Merging #104 (90918be) into master (9150f2d) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #104 +/- ##
=======================================
Coverage 62.61% 62.61%
=======================================
Files 132 132
Lines 4917 4917
=======================================
Hits 3079 3079
Misses 1838 1838
Flag | Coverage Δ | |
---|---|---|
unittests | 62.61% <ø> (ø) |
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 9150f2d...90918be. Read the comment docs.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
⚠️ Warning
``` google-auth 1.35.0 requires rsa, which is not installed. djangocms-picture 3.0.0 requires easy-thumbnails, which is not installed. django-polymorphic 3.0.0 has requirement Django>=2.1, but you have Django 1.11.29. django-filer 2.0.2 requires django-mptt, which is not installed. django-filer 2.0.2 requires easy-thumbnails, which is not installed. django-cms 3.8.0 has requirement Django>=2.2, but you have Django 1.11.29. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 3.1
SNYK-PYTHON-DJANGO-1066259
django:
1.11.29 -> 2.2.18
Why? Has a fix available, CVSS 3.3
SNYK-PYTHON-DJANGO-1279042
django:
1.11.29 -> 2.2.18
Why? Has a fix available, CVSS 7.3
SNYK-PYTHON-DJANGO-1290072
django:
1.11.29 -> 2.2.18
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-DJANGO-1298665
django:
1.11.29 -> 2.2.18
Why?
SNYK-PYTHON-LXML-1088006
lxml:
4.6.2 -> 4.6.3
Why?
SNYK-PYTHON-PILLOW-1055461
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1055462
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1059090
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1080635
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1080654
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1081494
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1081501
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1081502
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1082329
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1082750
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1090584
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1090586
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1090587
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1090588
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1292150
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1292151
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1316216
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-1319443
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-574573
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-574574
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-574575
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-574576
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-PILLOW-574577
pillow:
6.2.2 -> 8.1.0
Why?
SNYK-PYTHON-RSA-1038401
rsa:
4.5 -> 4.7
(*) 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 effected 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