Skip to content

[Snyk] Security upgrade axios from 1.12.0 to 1.13.5 - #18

Merged
hashim21223445 merged 1 commit into
masterfrom
snyk-fix-286d300a97304e19a3028559e0646279
Sep 4, 2026
Merged

[Snyk] Security upgrade axios from 1.12.0 to 1.13.5#18
hashim21223445 merged 1 commit into
masterfrom
snyk-fix-286d300a97304e19a3028559e0646279

Conversation

@hashim21223445

Copy link
Copy Markdown
Owner

snyk-top-banner

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
high severity 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

@semanticdiff-com

semanticdiff-com Bot commented Feb 16, 2026

Copy link
Copy Markdown

Review changes with  SemanticDiff

Changed Files
File Status
  package-lock.json  18% smaller
  package.json  0% smaller

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @hashim21223445, I'm Gemini Code Assist1! 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, automatically generated by Snyk, focuses on enhancing the project's security posture by upgrading the axios package to mitigate a known "Prototype Pollution" vulnerability. Beyond this critical fix, the update also encompasses a broad refresh of development dependencies, particularly within the ESLint ecosystem, ensuring the project benefits from the latest features, bug fixes, and security improvements across its toolchain.

Highlights

  • Security Upgrade for Axios: The axios package has been upgraded from version 1.12.0 to 1.13.5 to address a high-severity "Prototype Pollution" vulnerability (SNYK-JS-AXIOS-15252993).
  • ESLint Ecosystem Updates: Several ESLint-related development dependencies, including @typescript-eslint/eslint-plugin and eslint itself, have been significantly updated, bringing in newer versions of their sub-dependencies and removing some older ones.
  • General Dependency Refresh: Numerous other direct and transitive dependencies across the project have been updated to their latest compatible versions, improving overall package health and potentially performance.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • package-lock.json
    • Updated the axios dependency from 1.12.0 to 1.13.5.
    • Updated @typescript-eslint/eslint-plugin from 4.27.0 to 5.62.0.
    • Updated eslint from 7.29.0 to 9.39.2.
    • Updated acorn-jsx from 5.3.1 to 5.3.2.
    • Updated cross-spawn from 7.0.3 to 7.0.6.
    • Updated deep-is from 0.1.3 to 0.1.4.
    • Updated file-entry-cache from 6.0.1 to 8.0.0.
    • Updated flat-cache from 3.0.4 to 4.0.1.
    • Updated flatted from 3.1.1 to 3.3.3.
    • Updated form-data from 4.0.4 to 4.0.5.
    • Updated globals from 13.9.0 to 14.0.0.
    • Updated import-fresh from 3.3.0 to 3.3.1.
    • Updated is-glob from 4.0.1 to 4.0.3.
    • Updated js-yaml from 3.14.1 to 4.1.1.
    • Updated minimatch from 3.0.4 to 3.1.2.
    • Updated optionator from 0.9.1 to 0.9.4.
    • Updated parent-module from 1.0.1 to 1.0.1 (license added).
    • Updated semver from 7.3.5 to 7.7.4.
    • Updated type-check from 0.4.0 to 0.4.0 (license added).
    • Updated word-wrap from 1.2.3 to 1.2.5.
    • Removed @babel/code-frame, @babel/highlight and its sub-dependencies.
    • Removed ansi-colors, ansi-regex, astral-regex, doctrine, emoji-regex, enquirer, functional-red-black-tree, is-fullwidth-code-point, lodash.clonedeep, lodash.truncate, progress, regexpp, slice-ansi, sprintf-js, string-width, strip-ansi, table, text-table.
    • Added @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/semver, graphemer, json-buffer, keyv.
  • package.json
    • Updated the axios dependency to version ^1.13.5.
Activity
  • Snyk automatically created this pull request to address identified vulnerabilities.
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.

@snyk-io

snyk-io Bot commented Feb 16, 2026

Copy link
Copy Markdown

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

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

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

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly upgrades axios from version 1.12.0 to 1.13.5, addressing a security vulnerability. This is a necessary and welcome change.

However, the PR also includes major version upgrades for several development dependencies, most notably eslint (from v7 to v9) and its related plugins. These are substantial upgrades that are unrelated to the axios security fix and could introduce breaking changes or require configuration updates for the project's linting rules.

To maintain a clear and focused change history, I recommend separating these changes. This pull request should be scoped to only the axios upgrade. The developer dependency upgrades should be moved to a separate pull request where they can be reviewed and tested independently. This will make the changes easier to manage and revert if necessary.

Comment thread package-lock.json
Comment on lines +24 to +26
"@typescript-eslint/eslint-plugin": "^5.10.0",
"@typescript-eslint/parser": "^4.33.0",
"eslint": "^7.14.0",
"eslint": "^9.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

While the main goal of this PR is to upgrade axios for security reasons, it also includes major version upgrades for eslint (from v7 to v9) and @typescript-eslint/eslint-plugin (from v4 to v5). These are significant changes that could introduce breaking changes to the linting setup and should be handled in a separate pull request to allow for proper testing and review. This PR should focus solely on the axios upgrade.

@hashim21223445 hashim21223445 self-assigned this Sep 4, 2026
@hashim21223445 hashim21223445 added this to the Go collège milestone Sep 4, 2026
@hashim21223445 hashim21223445 added merge when passing Merge the PR automatically once all status checks have passed patch version Automatically create a new patch version tag after PR is merged minor version Automatically create a new minor version tag after PR is merged major version Automatically create a new major version tag after PR is merged dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 4, 2026
@hashim21223445
hashim21223445 merged commit c3de3b1 into master Sep 4, 2026
3 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code major version Automatically create a new major version tag after PR is merged merge when passing Merge the PR automatically once all status checks have passed minor version Automatically create a new minor version tag after PR is merged patch version Automatically create a new patch version tag after PR is merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants