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

Security upgrade express from 4.19.2 to 4.21.0 #9

Conversation

SayuruRehan
Copy link
Collaborator

snyk-top-banner

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

Snyk changed the following file(s):

  • notification-microservice/package.json
  • notification-microservice/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
low severity Cross-site Scripting
SNYK-JS-SEND-7926862
  391  

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:

🦉 Cross-site Scripting

…ce/package-lock.json to reduce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-SEND-7926862
@mrmihi mrmihi changed the title [Snyk] Security upgrade express from 4.19.2 to 4.21.0 Security upgrade express from 4.19.2 to 4.21.0 Sep 26, 2024
@SayuruRehan SayuruRehan changed the base branch from master to sayuru-vulnerability-fixes September 26, 2024 15:11
@SayuruRehan SayuruRehan merged commit 348b602 into sayuru-vulnerability-fixes Sep 26, 2024
1 check passed
@SayuruRehan SayuruRehan deleted the snyk-fix-7c86caeb55c22e4860f4893292cbc5d0 branch September 26, 2024 15:13
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