[Snyk] Security upgrade express from 4.17.1 to 4.20.0

[Exnadella]

User description

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

Snyk changed the following file(s):

• packages/polyserve/package.json
• packages/polyserve/package-lock.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)

---

PR Type

enhancement, dependencies

---

Description

• Upgraded the express dependency from version 4.8.5 to 4.20.0 in package.json to address security vulnerabilities.
• Updated package-lock.json to reflect the changes in the express dependency version.
• This upgrade addresses a Regular Expression Denial of Service (ReDoS) vulnerability identified by Snyk.

---

Changes walkthrough 📝

	Relevant files
Dependencies	package.json Upgrade express dependency to address vulnerabilities        packages/polyserve/package.json Upgraded express dependency from version 4.8.5 to 4.20.0. +1/-1      package-lock.json Update package-lock.json for express upgrade                          packages/polyserve/package-lock.json Updated lock file to reflect the upgraded express dependency. +5621/-5429
Additional files (token-limit)	package-lock.json ...                                                                                                            packages/polyserve/package-lock.json ... +5621/-5429

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[qodo-merge-pro]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[qodo-merge-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Enhancement	Update multiple dependencies to their latest compatible versions Consider updating other dependencies to their latest compatible versions to ensure optimal performance and security. packages/polyserve/package.json [50-53] "express": "^4.20.0", +"cors": "^2.8.5", +"http-proxy-middleware": "^2.0.6", +"lru-cache": "^7.14.1", Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion to update other dependencies to their latest compatible versions is valid for maintaining optimal performance and security. However, it is not crucial unless there are known vulnerabilities or issues with the current versions.	7

💡 Need additional feedback ? start a PR chat

[qodo-merge-pro]

CI Failure Feedback 🧐

(Checks updated until commit 2f276bd)

Action: test (ubuntu-latest)

Failed stage: Run npm run bootstrap [❌]

Failed test name: ""

Failure summary: The action failed due to an error during the execution of the npm ci command within the 'wct-mocha' package. The command exited with code 1, indicating a failure. The log also contains multiple warnings about deprecated packages, which might contribute to the failure.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 554: npm WARN deprecated [email protected]: this library is no longer supported 555: npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported 556: npm WARN deprecated [email protected]: This module is no longer supported. 557: npm WARN deprecated [email protected]: This package is no longer supported. 558: npm WARN deprecated [email protected]: This package is no longer supported. 559: npm WARN deprecated [email protected]: This package is no longer supported. 560: npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 561: npm WARN deprecated [email protected]: This package is no longer supported. 562: npm WARN deprecated @lerna/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. ... 737: npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links] 738: npm ERR! 739: npm ERR! aliases: clean-install, ic, install-clean, isntall-clean 740: npm ERR! 741: npm ERR! Run "npm help ci" for more info 742: npm ERR! A complete log of this run can be found in: 743: npm ERR! /home/runner/.npm/_logs/2024-09-18T19_22_14_260Z-debug-0.log 744: lerna ERR! npm ci exited 1 in 'wct-mocha' 745: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.