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
```
luigi 3.1.1 requires tenacity, which is not installed.
librosa 0.7.2 requires resampy, which is not installed.
dcase-util 0.2.20 requires validators, which is not installed.
```
(*) 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.
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
``` luigi 3.1.1 requires tenacity, which is not installed. librosa 0.7.2 requires resampy, which is not installed. dcase-util 0.2.20 requires validators, which is not installed. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 5.3
SNYK-PYTHON-NUMBA-1027297
numba:
0.48.0 -> 0.49.0
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321964
numpy:
1.19.2 -> 1.22.2
Why? Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321966
numpy:
1.19.2 -> 1.22.2
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321969
numpy:
1.19.2 -> 1.22.2
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321970
numpy:
1.19.2 -> 1.22.2
Why? Recently disclosed, Has a fix available, CVSS 3.1
SNYK-PYTHON-SETUPTOOLS-3113904
setuptools:
39.0.1 -> 65.5.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 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:
🦉 Denial of Service (DoS) 🦉 Denial of Service (DoS) 🦉 Regular Expression Denial of Service (ReDoS)