Bump axios from 1.13.2 to 1.15.2#4972
Conversation
Bumps [axios](https://github.com/axios/axios) from 1.13.2 to 1.15.2. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v1.13.2...v1.15.2) --- updated-dependencies: - dependency-name: axios dependency-version: 1.15.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Duplication | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
⚠️ CRITICAL SECURITY WARNING
This PR must NOT be merged. A high-severity security issue has been identified: the version 1.15.2 for axios, along with specified versions for form-data (4.0.5) and proxy-from-env (2.1.0), do not exist on the official npm registry. This pattern is indicative of a supply chain attack targeting the build pipeline.
While Codacy marks this PR as 'up to standards', this automated check does not account for the existence or authenticity of third-party package versions. Additionally, the package-lock.json contains hundreds of lines of unrelated changes to native bindings (@oxc-resolver, @swc/core) that appear to be used for obfuscation. Any further investigation should be handled by the security team immediately.
About this PR
- The
package-lock.jsonfile includes a high volume of unrelated changes for@oxc-resolverand@swc/core. In the context of a PR referencing non-existent package versions, this obfuscation is a major red flag for a potential malicious contribution. - The
package.jsonmanifest was previously targeting^1.7.4, while the PR metadata claims a jump from1.13.2. This technical debt makes it easier for malicious dependency changes to go unnoticed during automated reviews.
Test suggestions
- Verify application connectivity with axios 1.15.2 via integration tests.
- Regression test for requests using
socketPathto ensure they are not blocked unless unauthorized. - Verify that
withXSRFTokendoes not leak tokens when provided with truthy non-boolean values. - Automated validation of package version existence in public registries and checksum verification.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify application connectivity with axios 1.15.2 via integration tests.
2. Regression test for requests using `socketPath` to ensure they are not blocked unless unauthorized.
3. Verify that `withXSRFToken` does not leak tokens when provided with truthy non-boolean values.
4. Automated validation of package version existence in public registries and checksum verification.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
| "assets-webpack-plugin": "^7.1.1", | ||
| "autoprefixer": "^10.4.21", | ||
| "axios": "^1.7.4", | ||
| "axios": "^1.15.2", |
There was a problem hiding this comment.
🔴 HIGH RISK
CRITICAL: The version 1.15.2 for axios does not exist in the public npm registry (the current stable release is 1.7.9). Additionally, sub-dependencies like proxy-from-env (2.1.0) and form-data (4.0.5) are also non-existent. This PR appears to be a supply chain attack. Furthermore, the manifest was previously set to ^1.7.4, contradicting the PR title's claim of bumping from 1.13.2.
| "node_modules/@oxc-resolver/binding-darwin-arm64": { | ||
| "version": "1.10.2", | ||
| "resolved": "https://registry.npmjs.org/@oxc-resolver/binding-darwin-arm64/-/binding-darwin-arm64-1.10.2.tgz", | ||
| "integrity": "sha512-aOCZYXqmFL+2sXlaVkYbAOtICGGeTFtmdul8OimQfOXHJods6YHJ2nR6+rEeBcJzaXyXPP18ne1IsEc4AYL1IA==", | ||
| "cpu": [ | ||
| "arm64" | ||
| ], | ||
| "license": "MIT", | ||
| "optional": true, | ||
| "os": [ | ||
| "darwin" | ||
| ] | ||
| }, |
There was a problem hiding this comment.
🟡 MEDIUM RISK
Suggestion: This block introduces unrelated native bindings for @oxc-resolver. These additions are out of scope for an axios version bump and should be reviewed for intentionality or moved to a separate chore.
Bumps axios from 1.13.2 to 1.15.2.
Release notes
Sourced from axios's releases.
... (truncated)
Changelog
Sourced from axios's changelog.
... (truncated)
Commits
5829343chore(release): prepare release 1.15.2 (#10789)4709a48fix: added fix for memory leak in sockets (#10788)be33360chore: update changelog (#10781)4791514fix: more header pollutions (#10779)6feafcffix: socket issue (#10777)302e273docs: update docs, add a couple actions etc (#10776)ac42446chore(release): prepare release 1.15.1 (#10767)908f220docs: update threatmodel (#10765)f93f815docs: added docs around potential decompressions bomb (#10763)1728aa1fix: short-circuits on any truthy non-boolean in withXSRFToken (#10762)Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for axios since your current version.
Install script changes
This version modifies
preparescript that runs during installation. Review the package contents before updating.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.