[Snyk] Security upgrade axios from 0.25.0 to 1.13.2

[snyk-io]

Snyk has created this PR to fix 1 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
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-15930944	209

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

[snyk-io]

The upgrade from axios v0.25.0 to v1.13.2 is a major version change that introduces significant and breaking API modifications, primarily from the v1.0.0 release. Direct migration will require code changes to avoid application failure.

Key Breaking Changes:

• ESM Import: The import statement must be changed from import { axios } from 'axios' to the default import import axios from 'axios'. [1]
• Request Headers: The headers.common property, used for setting common headers like Authorization, has been removed. Headers must now be set on the root headers object (e.g., config.headers.Authorization = ...). [1]
• Parameter Serialization: The methods for serializing URL parameters have undergone numerous breaking changes. You must review the latest documentation to ensure correct serialization. [1]
• Interceptors: The type signature for the config parameter in request interceptors has been updated, which may affect TypeScript projects. [1]
• Internal Exports: Previously accessible internal functions are no longer exported. Code relying on these will break. [1]

Source: Upgrade guide v0.x to v1.x
Recommendation: This upgrade requires a developer to manually review and refactor code according to the official upgrade guide. Key areas to check are import statements, header manipulation, interceptors, and any custom parameter serialization logic.

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

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.