[Snyk] Security upgrade axios from 1.16.0 to 1.18.0

[rvu-snyk]

Snyk has created this PR to fix 10 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
	Uncontrolled Recursion SNYK-JS-AXIOS-18060730	738
	Prototype Pollution SNYK-JS-AXIOS-18065351	738
	Permissive List of Allowed Inputs SNYK-JS-AXIOS-18065357	738
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18060165	708
	Uncontrolled Recursion SNYK-JS-AXIOS-18060167	708
	Prototype Pollution SNYK-JS-AXIOS-18060659	708
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18060804	708
	Prototype Pollution SNYK-JS-AXIOS-18065349	708
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-18065353	708
	Prototype Pollution SNYK-JS-AXIOS-18065355	708

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Uncontrolled Recursion
🦉 Prototype Pollution
🦉 Allocation of Resources Without Limits or Throttling

[rvu-snyk]

This is a minor version upgrade that includes security hardening and behavioral changes that may require verification.

Behavioral Changes:

• Redirect Header Safety: In Node.js, sensitive headers specified by the caller may now be stripped on cross-origin redirects to prevent leakage of API keys or authentication tokens.
• URL Hardening: Malformed http: and https: URLs that are missing // will now be rejected with an ERR_INVALID_URL error.
• validateStatus Semantics: A new transitional option, validateStatusUndefinedResolves, has been added. This allows applications to opt-in to treating validateStatus: undefined as if the option was omitted.

Recommendation:
Review application logic related to cross-origin redirects, especially if custom sensitive headers are used. Ensure all URLs passed to Axios are well-formed. Test validateStatus behavior if your application relies on its specific handling.

Source: GitHub Release Notes

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