[peterj]

Snyk has created this PR to fix 12 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
	Prototype Pollution SNYK-JS-AXIOS-20245066	808
	Regular Expression Denial of Service (ReDoS) SNYK-JS-AXIOS-20245042	803
	Improper Validation of Specified Quantity in Input SNYK-JS-AXIOS-20245044	803
	Improper Validation of Specified Quantity in Input SNYK-JS-AXIOS-20245046	803
	Allocation of Resources Without Limits or Throttling SNYK-JS-AXIOS-20245062	803
	Unintended Proxy or Intermediary ('Confused Deputy') SNYK-JS-AXIOS-20245048	773
	Unintended Proxy or Intermediary ('Confused Deputy') SNYK-JS-AXIOS-20245056	743
	Server-side Request Forgery (SSRF) SNYK-JS-AXIOS-20245060	743
	Prototype Pollution SNYK-JS-AXIOS-20244996	738
	Prototype Pollution SNYK-JS-AXIOS-20245050	738
	Improper Input Validation SNYK-JS-AXIOS-20245058	738
	Prototype Pollution SNYK-JS-AXIOS-20245064	738

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:

🦉 Prototype Pollution
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Improper Input Validation
🦉 More lessons are available in Snyk Learn

[peterj]

This minor version upgrade for axios introduces several behavioral changes and stricter handling that could impact specific use cases.

Notable Changes:

• Stricter Length Limits: The fetch adapter now enforces maxBodyLength and maxContentLength. Requests that previously exceeded these unenforced limits will now fail. [1]
• Proxy Header Behavior: Proxy requests will now correctly preserve user-supplied Host headers. Applications that relied on the previous behavior may need to be updated. [1]
• Stricter Protocol Parsing: The parseProtocol function now strictly requires a colon (:) in the protocol separator, which may cause issues for malformed URLs that worked previously. [1]

Recommendation: While most applications will not be affected, it is important to verify functionality related to large request/response bodies (if using the fetch adapter) and proxy configurations. Test environments should be checked to ensure these changes do not introduce unexpected failures.

Source: GitHub Release Notes v1.20.0

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