Skip to content
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

[Snyk] Security upgrade @google-cloud/logging-winston from 4.1.0 to 6.0.0 #18

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tamnk74
Copy link
Owner

@tamnk74 tamnk74 commented Jul 27, 2024

snyk-top-banner

Snyk has created this PR to fix 5 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Open Redirect
SNYK-JS-NODEFORGE-2330875
  586  
high severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430339
  579  
medium severity Prototype Pollution
SNYK-JS-NODEFORGE-2331908
  529  
medium severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430337
  494  
medium severity Improper Verification of Cryptographic Signature
SNYK-JS-NODEFORGE-2430341
  494  

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.

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:

🦉 Open Redirect
🦉 Prototype Pollution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants