[Snyk] Fix for 4 vulnerabilities

[sidhantpanda]

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

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860	696
	Cross-site Scripting SNYK-JS-EXPRESS-7926867	541
	Cross-site Scripting SNYK-JS-SEND-7926862	391
	Cross-site Scripting SNYK-JS-SERVESTATIC-7926865	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

[github-actions]

Code Review:

Bug Risks:

1. Dependency Version Updates:
   • The versions of "body-parser" and "express" have been updated. Ensure that these updates do not introduce breaking changes in their APIs that could impact the behavior of your application.

Improvement Suggestions:

1. Check Compatibility:

   • Verify compatibility issues with the updated dependencies. Ensure they work well with other parts of your codebase.

2. Automated Testing:

   • Implement or update tests to ensure that functionality is maintained after these dependency updates.

3. Semantic Versioning:

   • Consider using semantic versioning ("~" or "^") for dependencies to allow minor updates that don't break compatibility.

4. Changelog Review:

   • Ensure to check the changelogs of updated packages to see if any critical changes have been made.

5. Security Audits:

   • Run security audits (if not already in place) to ensure the new versions do not introduce any vulnerabilities.

6. Regular Maintenance:

   • Schedule regular dependency updates to maintain a healthy and up-to-date codebase.

Remember to thoroughly test your application after these changes, especially focusing on areas affected by updated dependencies.