[Snyk] Security upgrade express from 4.18.3 to 4.20.0

[sidhantpanda]

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

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	738

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

[github-actions]

Code Review:

1. Library Updates:

   • The code patch updates the version of Express from 4.18.3 to 4.20.0. Make sure to review the release notes for Express 4.20.0 to check for any breaking changes or new features that might affect your application.

2. Risk/Bug Analysis:

   • Update dependencies could introduce breaking changes or bugs that were not present in the previous version. It is advisable to test the application after this update thoroughly to ensure everything works as expected.

3. Testing:

   • Perform comprehensive testing of the application, including both functional tests and regression tests, to catch any issues that might arise due to the library updates.

4. Security Checks:

   • Ensure that the updated libraries do not introduce any security vulnerabilities. Consider using tools like npm audit to check for vulnerabilities in your project dependencies.

5. Dependency Management:

   • Regularly review and update dependencies to keep them secure and up-to-date. Consider automating dependency checks and updates if possible.

6. Documentation:

   • Update documentation to reflect the new versions of libraries used in the project.

In summary, while updating libraries is essential for security and performance reasons, it's crucial to proceed cautiously, test thoroughly, and be prepared to address any issues that may arise due to these updates.