[Snyk] Fix for 1 vulnerabilities

[ryanoolala]

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

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

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

[Copilot]

Pull request overview

This is an automated Snyk security PR that upgrades three npm dependencies to fix vulnerability SNYK-JS-QS-14724253 (Allocation of Resources Without Limits or Throttling) with a severity score of 828/1000.

Key changes:

• Upgrades body-parser from 1.18.3 to 1.20.4 (minor version bump)
• Upgrades express from 4.17.1 to 4.22.0 (minor version bump)
• Upgrades superagent from 5.1.0 to 10.2.2 (major version jump across 5 major versions)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The upgrade to superagent from version 5.1.0 to 10.2.2 represents a major version jump (5 major versions), which typically introduces breaking changes. This is particularly concerning because:

1. The project uses superagent-proxy version 2.0.0, which may not be compatible with superagent 10.x
2. The API surface and behavior of superagent likely changed significantly between versions 5 and 10
3. The PR description indicates this is a breaking change (isBreakingChange: true in metadata)

The package-lock.json was not updated (as noted in the warning), which means the actual dependency resolution hasn't been tested. Before merging, you should:

• Verify that superagent-proxy ^2.0.0 is compatible with superagent ^10.2.2
• Update package-lock.json by running npm install
• Test the /send-test-request endpoint thoroughly to ensure the superagent API changes don't break functionality

Suggested change

	"superagent": "^10.2.2",
	"superagent": "^5.1.0",

[Copilot]

The package-lock.json file was not updated as part of this security fix (see warning in PR description). This means:

1. The actual resolved versions of transitive dependencies are unknown
2. The security fix may not be properly applied until package-lock.json is regenerated
3. CI/CD builds may fail or produce inconsistent results

You must run npm install locally and commit the updated package-lock.json before merging this PR to ensure the dependency tree is properly resolved and the security vulnerability is actually fixed.