SWI-3723 [Snyk] Fix for 1 vulnerabilities

[bwappsec]

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

Snyk changed the following file(s):

• assets/server/node/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	170

---

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

[bwappsec]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[bwappsec]

The primary risk in this set of upgrades comes from the major version jump for ngrok from v3 to v4.

ngrok: 3.2.7 → 4.0.0 (High Risk)
This upgrade introduces several breaking changes requiring developer action:

• Node.js Version: Support for Node.js versions below 14.2 is dropped.
• Authentication: The auth and httpauth tunnel options have been replaced with basic_auth.
• API Usage: The ngrok.getApi() method has been changed and now returns a new NgrokClient object.
• TypeScript: Type definitions have been restructured under the Ngrok namespace.

express: 4.17.1 → 4.22.0 (Low Risk)
This is a minor version upgrade that includes bug fixes and security patches with no documented breaking changes.

Recommendation: The ngrok upgrade requires code changes. Review usage of authentication options and any direct calls to the ngrok client API before merging.

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