Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
requirements.txt
⚠️ Warning
```
mixer 7.0.6 requires Faker, which is not installed.
django-tablib 3.2 requires tablib, which is not installed.
django-debug-toolbar 1.11.1 has requirement Django>=1.11, but you have Django 1.6.5.
django-debug-toolbar 1.11.1 has requirement sqlparse>=0.2.0, but you have sqlparse 0.1.19.
django-braces 1.14.0 has requirement Django>=1.11.0, but you have Django 1.6.5.
```
Vulnerabilities that will be fixed
By pinning:
Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity
706/1000 Why? Recently disclosed, Has a fix available, CVSS 8.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 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.
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
``` mixer 7.0.6 requires Faker, which is not installed. django-tablib 3.2 requires tablib, which is not installed. django-debug-toolbar 1.11.1 has requirement Django>=1.11, but you have Django 1.6.5. django-debug-toolbar 1.11.1 has requirement sqlparse>=0.2.0, but you have sqlparse 0.1.19. django-braces 1.14.0 has requirement Django>=1.11.0, but you have Django 1.6.5. ```Vulnerabilities that will be fixed
By pinning:
Why? Recently disclosed, Has a fix available, CVSS 8.2
SNYK-PYTHON-DJANGODEBUGTOOLBAR-1246398
django-debug-toolbar:1.3.0 -> 1.11.1(*) 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
This change is