chore(deps): bump dependencies with audit warnings to latest

[rexxars]

Description

Bumps dependencies that have audit warnings to their latest (or non-affected) versions.

In light of https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
sdk-docs	Error			Dec 3, 2025 9:09pm
sdk-kitchensink-react	Error			Dec 3, 2025 9:09pm

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	husky@​9.1.6 ⏵ 9.1.7
	@​commitlint/​types@​19.8.0 ⏵ 19.8.1
	@​vitest/​coverage-v8@​3.1.2 ⏵ 3.2.4			+1
	@​commitlint/​cli@​19.8.0 ⏵ 19.8.1
	@​sanity/​types@​3.88.1 ⏵ 3.99.0			+1
	typescript-eslint@​8.26.1 ⏵ 8.48.1			-1	+1
	@​types/​react-dom@​19.1.3 ⏵ 19.2.3	+1		+1
	@​sanity/​prettier-config@​1.0.3 ⏵ 1.0.6	+2		+2	+2
	@​sanity/​cli@​3.88.1-typegen-experimental.0 ⏵ 4.20.0	+1		+2
	vitest@​3.1.2 ⏵ 3.2.4
	@​types/​react@​19.1.2 ⏵ 19.2.7
	react-router@​7.5.2 ⏵ 7.10.0	-2		+1
	inter-ui@​4.1.0 ⏵ 4.1.1	+1		+1	+3
	@​types/​node@​22.13.9 ⏵ 22.19.1	+1		+1	+1
	tsx@​4.19.4 ⏵ 4.21.0	+8		+1	+6
	@​sanity/​icons@​3.7.0 ⏵ 3.7.4	+1		+1	+1
	eslint-plugin-react@​7.37.4 ⏵ 7.37.5	+1
	eslint-plugin-import@​2.31.0 ⏵ 2.32.0
	react@​19.1.0 ⏵ 19.2.1			+1	+1
	eslint-plugin-unused-imports@​4.1.4 ⏵ 4.3.0			+1
	globals@​16.0.0 ⏵ 16.5.0			+1
	@​sanity/​ui@​2.15.13 ⏵ 3.1.11	+1		+2
	minimatch@​3.0.8 ⏵ 10.1.1			+1
	eslint-plugin-react-refresh@​0.4.19 ⏵ 0.4.24	+1		+1
	turbo@​2.5.2 ⏵ 2.6.2	+1		+1	+2
	@​commitlint/​config-conventional@​19.8.0 ⏵ 19.8.1
	styled-components@​6.1.18 ⏵ 6.1.19	+1		+1
	json-edit-react@​1.26.2 ⏵ 1.29.0			+2	-2
	eslint-config-prettier@​10.1.1 ⏵ 10.1.8	+1		+1
	rimraf@​6.0.1 ⏵ 6.1.2	+1
	dotenv@​16.5.0 ⏵ 16.6.1	+1
	@​testing-library/​jest-dom@​6.6.3 ⏵ 6.9.1
See 22 more rows in the dashboard

View full report

[socket-security]

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		License policy violation: npm inter-ui under OFL-1.1 License: OFL-1.1 - the applicable license policy does not allow this license (4) (npm metadata) License: OFL-1.1 - the applicable license policy does not allow this license (4) (package/LICENSE.txt) License: OFL-1.1 - the applicable license policy does not allow this license (4) (package/package.json) From: apps/kitchensink-react/package.json → npm/[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/[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		License policy violation: npm typescript License: LicenseRef-W3C-Community-Final-Specification-Agreement - the applicable license policy does not allow this license (4) (package/ThirdPartyNoticeText.txt) From: apps/kitchensink-react/package.json → npm/[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/[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		Install-time scripts: npm unrs-resolver during postinstall Install script: postinstall Source: napi-postinstall unrs-resolver 1.11.1 check From: pnpm-lock.yaml → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is an install script? 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: Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[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.

View full report