(*) 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.
Coverage remained the same at 91.688% when pulling 497e6301d9e5e89bb4e2793ab39be03f051e0d6d on snyk-fix-6cc63fef8f4443faa659ea0319f5eac0 into 3503a1517d86ed272129028223b98cccbbcf1dde on master.
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
``` django-rq 0.9.1 requires django, which is not installed. ```Vulnerabilities that will be fixed
By pinning:
Why? Recently disclosed, Has a fix available, CVSS 3.3
SNYK-PYTHON-DJANGO-1279042
django:
1.11 -> 2.2.21
(*) 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