[Snyk] Security upgrade axios from 1.12.2 to 1.13.5

[Dargon789]

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

• package.json
• yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Prototype Pollution SNYK-JS-AXIOS-15252993	828

---

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

[snyk-io]

⚠️ Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details

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

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates a critical security update for the project's dependencies. It specifically targets a high-severity vulnerability found in the axios package, ensuring the application remains secure against known exploits. The changes involve updating the primary dependency version and subsequently synchronizing the entire dependency lockfile to maintain consistency and integrity across the project's package ecosystem.

Highlights

• Security Upgrade for Axios: The axios package has been upgraded from version 1.12.2 to 1.13.5 to address a high-severity 'Prototype Pollution' vulnerability (SNYK-JS-AXIOS-15252993).
• Dependency Lockfile Synchronization: The yarn.lock file has been extensively updated to reflect the new axios version and synchronize the entire dependency tree, including numerous transitive dependency updates and removals.

Changelog

• package.json
  • Updated the axios dependency version from 1.12.2 to 1.13.5.
• yarn.lock
  • Synchronized the lockfile to reflect the axios version upgrade.
  • Updated various transitive dependencies, including several @eslint related packages, @humanwhocodes packages, acorn, ajv, follow-redirects, form-data, flat-cache, flatted, glob-parent, globals, js-yaml, optionator, strip-json-comments, and word-wrap.
  • Added new dependencies such as @eslint-community/eslint-utils, @eslint-community/regexpp, @eslint/config-array, @eslint/config-helpers, @eslint/core, @eslint/js, @eslint/plugin-kit, @humanfs/core, @humanfs/node, @humanwhocodes/module-importer, @humanwhocodes/retry, @types/estree, @types/json-schema, json-buffer, and keyv.
  • Removed outdated or unused dependencies like doctrine@^3.0.0, grapheme-splitter@^1.0.4, text-table@^0.2.0, type-fest@^0.20.2, and v8-compile-cache@^2.0.3.

Activity

• This pull request was automatically generated by Snyk to address a detected security vulnerability.
• Snyk identified a high-severity 'Prototype Pollution' vulnerability in the axios package and proposed an upgrade to fix it.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the axios dependency from version 1.12.2 to 1.13.5 to address a high-severity prototype pollution vulnerability. The change is correct and necessary for security. I've suggested a minor improvement in package.json to use a caret range for the axios version. This will help in automatically receiving future non-breaking security patches and bug fixes, improving the long-term maintainability of the project.

[gemini-code-assist]

While pinning the axios version to 1.13.5 resolves the current security vulnerability, it's better practice to use a caret (^) to allow for automatic patch and minor updates. This ensures that you receive future non-breaking security fixes and bug fixes without needing to manually update the package.json file each time.

I suggest changing the version to ^1.13.5.

Suggested change

	"axios": "1.13.5"
	"axios": "^1.13.5"