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:
test/requirements.txt
⚠️ Warning
```
s3transfer 0.2.1 requires botocore, which is not installed.
Jinja2 2.11.3 requires MarkupSafe, which is not installed.
hca 6.3.0 requires cryptography, which is not installed.
hca 6.3.0 requires botocore, which is not installed.
hca 6.3.0 requires awscli, which is not installed.
hca 6.3.0 has requirement rsa<=3.5.0,>=3.1.2, but you have rsa 4.9.
google-auth-oauthlib 0.7.0 has requirement google-auth>=2.13.0, but you have google-auth 1.35.0.
boto3 1.25.4 requires botocore, which is not installed.
boto3 1.25.4 has requirement s3transfer<0.7.0,>=0.6.0, but you have s3transfer 0.2.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.
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
``` s3transfer 0.2.1 requires botocore, which is not installed. Jinja2 2.11.3 requires MarkupSafe, which is not installed. hca 6.3.0 requires cryptography, which is not installed. hca 6.3.0 requires botocore, which is not installed. hca 6.3.0 requires awscli, which is not installed. hca 6.3.0 has requirement rsa<=3.5.0,>=3.1.2, but you have rsa 4.9. google-auth-oauthlib 0.7.0 has requirement google-auth>=2.13.0, but you have google-auth 1.35.0. boto3 1.25.4 requires botocore, which is not installed. boto3 1.25.4 has requirement s3transfer<0.7.0,>=0.6.0, but you have s3transfer 0.2.1. ```Vulnerabilities that will be fixed
By pinning:
Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-CRYPTOGRAPHY-1022152
cryptography:2.3.1 -> 3.2Why? Has a fix available, CVSS 7.5
SNYK-PYTHON-RSA-1038401
rsa:3.4.2 -> 4.7Why? Has a fix available, CVSS 5.6
SNYK-PYTHON-RSA-570831
rsa:3.4.2 -> 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 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:
🦉 Access Restriction Bypass