[Snyk] Fix for 1 vulnerabilities

[wasimakh2]

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 PR fixes a high-severity security vulnerability (SNYK-JS-QS-14724253, score 828) related to "Allocation of Resources Without Limits or Throttling" in the qs package, which is a transitive dependency. The fix requires updating multiple packages that depend on qs.

Key Changes:

• Updates body-parser from 1.18.3 to 1.20.4 to resolve the qs vulnerability
• Updates express from 4.17.1 to 4.22.0 for compatibility and security
• Updates juice, node-gcm, and turndown with major version bumps to maintain compatibility

---

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

[Copilot]

The version specifier for body-parser has been updated without a caret (^) prefix, which means it will only accept exactly version 1.20.4. This is inconsistent with most other dependencies in this file which use caret ranges to allow minor and patch updates. Consider changing to ^1.20.4 to allow automatic security and bug fix updates within the 1.x version range.

Suggested change

	"body-parser": "1.20.4",
	"body-parser": "^1.20.4",

[Copilot]

The version specifier for node-gcm has been updated without a caret (^) prefix, which means it will only accept exactly version 1.1.0. This is inconsistent with most other dependencies in this file which use caret ranges to allow minor and patch updates. Consider changing to ^1.1.0 to allow automatic security and bug fix updates within the 1.x version range.

Suggested change

	"node-gcm": "1.1.0",
	"node-gcm": "^1.1.0",

[Copilot]

This update involves a major version jump from 5.x to 7.x, skipping version 6 entirely. Major version updates typically include breaking changes that may affect functionality. It's recommended to review the CHANGELOG and migration guides for juice versions 6.0.0 and 7.0.0 to ensure compatibility with your current usage, particularly around CSS inlining behavior and API changes.

Suggested change

	"juice": "^7.0.0",
	"juice": "^5.0.0",

[Copilot]

This update involves a major version jump from 0.x to 1.x. Major version updates typically include breaking changes. Note that node-gcm is a deprecated library (Google Cloud Messaging has been deprecated in favor of Firebase Cloud Messaging). Consider migrating to a modern Firebase Cloud Messaging library in the future to avoid using deprecated services.

Suggested change

	"node-gcm": "1.1.0",
	"node-gcm": "^0.14.0",