[Snyk] Security upgrade axios from 1.15.2 to 1.18.0

[macroscope-cloud]

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

Snyk changed the following file(s):

• package.json
• package-lock.json

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:

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

[macroscope-cloud]

This upgrade of axios from v1.15.2 to v1.18.0 includes several security-driven behavioral changes and stricter validation that require verification.

Key Changes:

• Stricter URL Handling:
  • URLs that omit // after http: or https: will now be rejected with an ERR_INVALID_URL error. [1, 4]
  • The protocol parser now strictly requires a colon (:) in the protocol separator. Strings that were previously loosely parsed may no longer match. [1, 4]
• Redirect Security: In Node.js, sensitive headers (like Authorization) will now be stripped from requests during cross-origin redirects to prevent credentials from leaking. [1, 2, 4]
• Encoding Changes: The deprecated unescape() function has been replaced with modern UTF-8 encoding for URLs. This may change the output for non-ASCII URLs if the application was relying on the previous non-standard behavior. [1, 4]

Recommendation:
While no APIs were removed, these changes in validation and security hardening could affect applications that rely on previous, less-strict behaviors. It is recommended to test URL parsing, cross-origin redirects that involve authentication, and handling of non-ASCII characters in URLs.

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.