Skip to content

[Snyk] Security upgrade express from 4.18.2 to 4.22.0#12

Open
danpetitt wants to merge 1 commit intomainfrom
snyk-fix-d8ea86a9d18cbbfcfb73a65365caddb2
Open

[Snyk] Security upgrade express from 4.18.2 to 4.22.0#12
danpetitt wants to merge 1 commit intomainfrom
snyk-fix-d8ea86a9d18cbbfcfb73a65365caddb2

Conversation

@danpetitt
Copy link
Member

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):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-14724253
  828  

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:

🦉 Allocation of Resources Without Limits or Throttling

@danpetitt
Copy link
Member Author

Merge Risk: Low

This is a minor version update that, according to the official changelog, contains no breaking changes. The upgrade from 4.18.2 to 4.22.0 consists of bug fixes, security patches, and backward-compatible feature additions. One notable change is the deprecation of res.location("back") and res.redirect("back") in version 4.21.0, which developers should be aware of for future code maintenance. [1]

Source: Package documentation
Recommendation: This update is considered safe to merge.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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