Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

[Snyk] Security upgrade snowflake-connector-python from 3.0.4 to 3.12.3 #39

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

Open
cpdough wants to merge 1 commit into main
base: main
Choose a base branch
Loading
from snyk-fix-b159983c181a57a73e2ae9aced591b2d

Conversation

@cpdough
Copy link

@cpdough cpdough commented Nov 1, 2024

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • requirements.txt
⚠️ Warning 
xgboost 1.6.2 requires scipy, which is not installed.
sweetviz 2.3.1 requires scipy, which is not installed.
statsmodels 0.13.5 requires scipy, which is not installed.
statsmodels 0.13.5 requires scipy, which is not installed.
scikit-learn 1.0.2 requires scipy, which is not installed.
pyrasgo 2023年5月1日 requires snowflake-connector-python, which is not installed.
pyrasgo 2023年5月1日 requires snowflake-connector-python, which is not installed.
category-encoders 2.6.4 requires scipy, which is not installed.
catboost 1.2.7 requires scipy, which is not installed.

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • 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.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Insertion of Sensitive Information into Log File

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

AltStyle によって変換されたページ (->オリジナル) /