-
Notifications
You must be signed in to change notification settings - Fork 347
[Snyk] Security upgrade numpy from 1.16.5 to 1.22.0 #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The following vulnerabilities are fixed by pinning transitive dependencies: - https://snyk.io/vuln/SNYK-PYTHON-NUMPY-2321966
Kudos, SonarCloud Quality Gate passed! Quality Gate passed
Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells
No Coverage information No Coverage information
No Duplication information No Duplication information
ghost
commented
Jan 2, 2022
Sider has detected 1 warning on analyzing the commit c9bdbf0.
⚠️ Goodcheck
If the errors persist even after retrying, the following actions may resolve them:
- Update tool dependencies
- Configure failed tools
- Configure
sider.yml - Turn off unused tools
If you still have problems, feel free to ask us via chat. 💬
You can turn off such notifications if unnecessary.
1 similar comment
ghost
commented
Jan 2, 2022
Sider has detected 1 warning on analyzing the commit c9bdbf0.
⚠️ Goodcheck
If the errors persist even after retrying, the following actions may resolve them:
- Update tool dependencies
- Configure failed tools
- Configure
sider.yml - Turn off unused tools
If you still have problems, feel free to ask us via chat. 💬
You can turn off such notifications if unnecessary.
Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR
Vulnerabilities that will be fixed
By pinning:
Why? Recently disclosed, Has a fix available, CVSS 3.7
SNYK-PYTHON-NUMPY-2321966
numpy:1.16.5 -> 1.22.0(*) 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