chore(deps): bump axios from 1.10.0 to 1.12.2 #7

dependabot · 2025-10-01T01:39:10Z

Bumps axios from 1.10.0 to 1.12.2.

Release notes

Release v1.12.2

Release notes:

Bug Fixes

fetch: use current global fetch instead of cached one when env fetch is not specified to keep MSW support; (#7030) (cf78825)

Contributors to this release

Dmitriy Mozgovoy

Noritaka Kobayashi

Release v1.12.1

Release notes:

Bug Fixes

types: fixed env config types; (#7020) (b5f26b7)

Contributors to this release

Dmitriy Mozgovoy

Release v1.12.0

Release notes:

Bug Fixes

adding build artifacts (9ec86de)

dont add dist on release (a2edc36)

fetch-adapter: set correct Content-Type for Node FormData (#6998) (a9f47af)

node: enforce maxContentLength for data: URLs (#7011) (945435f)

package exports (#5627) (aa78ac2)

params: removing '[' and ']' from URL encode exclude characters (#3316) (#5715) (6d84189)

release pr run (fd7f404)

types: change the type guard on isCancel (#5595) (0dbb7fd)

Features

adapter: surface low‑level network error details; attach original error via cause (#6982) (78b290c)

fetch: add fetch, Request, Response env config variables for the adapter; (#7003) (c959ff2)

support reviver on JSON.parse (#5926) (2a97634), closes #5924

types: extend AxiosResponse interface to include custom headers type (#6782) (7960d34)

Contributors to this release

Willian Agostini

Dmitriy Mozgovoy

khani

Ameer Assadi

Emiedonmokumo Dick-Boro

Zeroday BYTE

... (truncated)

Changelog

Sourced from axios's changelog.

1.12.2 (2025-09-14)

Bug Fixes

fetch: use current global fetch instead of cached one when env fetch is not specified to keep MSW support; (#7030) (cf78825)

Contributors to this release

Dmitriy Mozgovoy

Noritaka Kobayashi

1.12.1 (2025-09-12)

Bug Fixes

types: fixed env config types; (#7020) (b5f26b7)

Contributors to this release

Dmitriy Mozgovoy

1.12.0 (2025-09-11)

Bug Fixes

adding build artifacts (9ec86de)

dont add dist on release (a2edc36)

fetch-adapter: set correct Content-Type for Node FormData (#6998) (a9f47af)

node: enforce maxContentLength for data: URLs (#7011) (945435f)

package exports (#5627) (aa78ac2)

params: removing '[' and ']' from URL encode exclude characters (#3316) (#5715) (6d84189)

release pr run (fd7f404)

types: change the type guard on isCancel (#5595) (0dbb7fd)

Features

adapter: surface low‑level network error details; attach original error via cause (#6982) (78b290c)

fetch: add fetch, Request, Response env config variables for the adapter; (#7003) (c959ff2)

support reviver on JSON.parse (#5926) (2a97634), closes #5924

types: extend AxiosResponse interface to include custom headers type (#6782) (7960d34)

Contributors to this release

Willian Agostini

Dmitriy Mozgovoy

khani

... (truncated)

Commits

e5a3336 chore(release): v1.12.2 (#7031)
38726c7 refactor: change if in else to else if (#7028)
cf78825 fix(fetch): use current global fetch instead of cached one when env fetch is ...
c26d00f refactor: remove redundant assignment (#7029)
9fb41a8 chore(ci): add local HTTP server for Karma tests; (#7022)
19f9f36 docs(readme): add custom fetch section; (#7024)
3cac78c chore(release): v1.12.1 (#7021)
b5f26b7 fix(types): fixed env config types; (#7020)
0d8ad6e chore(release): v1.12.0 (#7013)
fd7f404 fix: release pr run
Additional commits viewable in compare view

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 rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will 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 version will 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 dependency will 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.

Bumps [axios](https://github.com/axios/axios) from 1.10.0 to 1.12.2. - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md) - [Commits](axios/axios@v1.10.0...v1.12.2) --- updated-dependencies: - dependency-name: axios dependency-version: 1.12.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>

socket-security · 2025-10-01T01:39:57Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Quality	Maintenance
	@radix-ui/react-switch@1.2.5 ⏵ 1.2.6
	@radix-ui/react-collapsible@1.1.11 ⏵ 1.1.12
	@radix-ui/react-tabs@1.1.12 ⏵ 1.1.13
	@radix-ui/react-hover-card@1.1.14 ⏵ 1.1.15
	@radix-ui/react-checkbox@1.3.2 ⏵ 1.3.3
	@radix-ui/react-radio-group@1.3.7 ⏵ 1.3.8
	@radix-ui/react-dropdown-menu@2.1.15 ⏵ 2.1.16
	@radix-ui/react-alert-dialog@1.1.14 ⏵ 1.1.15
	@radix-ui/react-popover@1.1.14 ⏵ 1.1.15
	@radix-ui/react-accordion@1.2.11 ⏵ 1.2.12
	@radix-ui/react-dialog@1.1.14 ⏵ 1.1.15
	@radix-ui/react-menubar@1.1.15 ⏵ 1.1.16
	@radix-ui/react-tooltip@1.2.7 ⏵ 1.2.8
	@radix-ui/react-slider@1.3.5 ⏵ 1.3.6
	@radix-ui/react-scroll-area@1.2.9 ⏵ 1.2.10
	@radix-ui/react-navigation-menu@1.2.13 ⏵ 1.2.14
	@types/pg@8.15.4 ⏵ 8.15.5			^-2
	@radix-ui/react-select@2.2.5 ⏵ 2.2.6
	@types/semver@7.7.0 ⏵ 7.7.1		⁺¹
	@types/nodemailer@6.4.17 ⏵ 6.4.20			⁺⁶
	tsx@4.20.3 ⏵ 4.20.6
	react-aria@3.41.1 ⏵ 3.43.2	⁺¹	⁺²	⁺¹
	immer@10.1.1 ⏵ 10.1.3	⁺¹	⁺¹
	@turbo/gen@2.5.4 ⏵ 2.5.8		⁺²	⁺²
	pretty-ms@9.2.0 ⏵ 9.3.0	⁺¹	⁺¹
	match-sorter@8.0.3 ⏵ 8.1.0	⁺¹		^-2
	@date-fns/tz@1.2.0 ⏵ 1.4.1
	turbo@2.5.4 ⏵ 2.5.8	⁺¹	⁺²	⁺²
	react-stately@3.39.0 ⏵ 3.41.0	⁺¹	⁺¹
	@tanstack/react-query@5.81.5 ⏵ 5.90.2		⁺¹	^-1
	@opentelemetry/semantic-conventions@1.34.0 ⏵ 1.37.0	⁺¹
	@opentelemetry/exporter-jaeger@2.0.1 ⏵ 2.1.0	⁺¹		⁺⁵
	@octokit/webhooks@13.9.0 ⏵ 13.9.1		⁺¹
See 17 more rows in the dashboard

View full report

socket-security · 2025-10-01T01:39:59Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/[email protected]` → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`@swagger-api/[email protected]` has a License Policy Violation. License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) License: AFL-3.0 (package/LICENSES/AFL-3.0.txt) From: pnpm-lock.yaml → `npm/@swagger-api/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@swagger-api/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
See 8 more rows in the dashboard

View full report

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 1, 2025

dependabot bot mentioned this pull request Oct 1, 2025

chore(deps): bump axios from 1.10.0 to 1.11.0 #6

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): bump axios from 1.10.0 to 1.12.2 #7

chore(deps): bump axios from 1.10.0 to 1.12.2 #7

Uh oh!

dependabot bot commented on behalf of github Oct 1, 2025

Uh oh!

socket-security bot commented Oct 1, 2025

Uh oh!

socket-security bot commented Oct 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

chore(deps): bump axios from 1.10.0 to 1.12.2 #7

Are you sure you want to change the base?

chore(deps): bump axios from 1.10.0 to 1.12.2 #7

Uh oh!

Conversation

dependabot bot commented on behalf of github Oct 1, 2025

Release v1.12.2

Release notes:

Bug Fixes

Contributors to this release

Release v1.12.1

Release notes:

Bug Fixes

Contributors to this release

Release v1.12.0

Release notes:

Bug Fixes

Features

Contributors to this release

1.12.2 (2025-09-14)

Bug Fixes

Contributors to this release

1.12.1 (2025-09-12)

Bug Fixes

Contributors to this release

1.12.0 (2025-09-11)

Bug Fixes

Features

Contributors to this release

Uh oh!

socket-security bot commented Oct 1, 2025

Uh oh!

socket-security bot commented Oct 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants