[Snyk] Security upgrade express from 4.17.1 to 4.21.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/web-component-tester/package.json
• packages/web-component-tester/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	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

---

PR Type

enhancement, bug fix

---

Description

• Upgraded the express package from version 4.15.3 to 4.21.0 in package.json to address a Cross-site Scripting vulnerability.
• Updated package-lock.json to ensure consistency with the new express version.
• This upgrade fixes the vulnerability identified by Snyk with ID SNYK-JS-SEND-7926862.

---

Changes walkthrough 📝

	Relevant files
Enhancement	package.json Upgrade express dependency to address vulnerabilities        packages/web-component-tester/package.json Upgraded express dependency from version 4.15.3 to 4.21.0. +1/-1      package-lock.json Update package-lock.json for express upgrade                          packages/web-component-tester/package-lock.json Updated lock file to reflect the upgraded express dependency. +11985/-11896
Additional files (token-limit)	package-lock.json ...                                                                                                            packages/web-component-tester/package-lock.json ... +11985/-11896

---

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

[codiumai-pr-agent-pro]

PR Reviewer Guide 🔍

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[codiumai-pr-agent-pro]

PR Code Suggestions ✨

Category	Suggestion	Score
Enhancement	Update multiple dependencies to their latest compatible versions Consider updating other dependencies alongside express to ensure compatibility and take advantage of the latest features and security fixes. packages/web-component-tester/package.json [65-68] "express": "^4.21.0", +"chalk": "^4.1.2", +"glob": "^8.0.3", +"lodash": "^4.17.21", Apply this suggestion Suggestion importance[1-10]: 7 Why: Updating other dependencies like chalk, glob, and lodash to their latest versions can improve compatibility, security, and performance. However, this is a suggestion for enhancement rather than a critical fix, hence a moderate score.	7

[codiumai-pr-agent-pro]

CI Failure Feedback 🧐

(Checks updated until commit 751d8d0)

Action: test (ubuntu-latest)

Failed stage: Run npm run bootstrap [❌]

Failure summary: The action failed because the npm ci command exited with code 1 in the 'wct-mocha' package. This indicates that there was an error during the installation of dependencies. Additionally, there are multiple deprecation warnings for various npm packages, which might be related to the failure.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 564: npm WARN deprecated glob@7.1.4: Glob versions prior to v9 are no longer supported 565: npm WARN deprecated fs-write-stream-atomic@1.0.10: This package is no longer supported. 566: npm WARN deprecated figgy-pudding@3.5.1: This module is no longer supported. 567: npm WARN deprecated copy-concurrently@1.0.5: This package is no longer supported. 568: npm WARN deprecated debuglog@1.0.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 569: npm WARN deprecated gauge@2.7.4: This package is no longer supported. 570: npm WARN deprecated are-we-there-yet@1.1.5: This package is no longer supported. 571: npm WARN deprecated @lerna/write-log-file@3.13.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. 572: npm WARN deprecated @lerna/validation-error@3.13.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. ... 746: npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links] 747: npm ERR! 748: npm ERR! aliases: clean-install, ic, install-clean, isntall-clean 749: npm ERR! 750: npm ERR! Run "npm help ci" for more info 751: npm ERR! A complete log of this run can be found in: 752: npm ERR! /home/runner/.npm/_logs/2024-09-12T20_51_32_404Z-debug-0.log 753: lerna ERR! npm ci exited 1 in 'wct-mocha' 754: ##[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.