Config updates

[secbajor]

No description provided.

[vercel]

@diterra-code is attempting to deploy a commit to the bleu Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​radix-ui/​react-slot@​1.1.2 ⏵ 1.2.3			-3
	@​radix-ui/​react-tabs@​1.1.3 ⏵ 1.1.13			-3
	@​radix-ui/​react-popover@​1.1.6 ⏵ 1.1.15			-3
	@​radix-ui/​react-dialog@​1.1.6 ⏵ 1.1.15			-3
	@​radix-ui/​react-tooltip@​1.1.8 ⏵ 1.2.8			-3
	urql@​4.2.1 ⏵ 4.2.2				+8
	@​types/​react-dom@​19.0.4 ⏵ 19.1.9	+1		+1
	wagmi@​2.14.11 ⏵ 2.16.9	+1		+1	-1
	@​types/​react@​19.0.10 ⏵ 19.1.12	+1		+1
	@​tailwindcss/​postcss@​4.0.7 ⏵ 4.1.13	+1		+2
	@​types/​node@​22.13.4 ⏵ 22.18.1	+1		+1
	postcss@​8.5.2 ⏵ 8.5.6	+1		+1
	tailwindcss@​4.0.7 ⏵ 4.1.13			-1
	react@​19.0.0 ⏵ 18.3.1			+1
	graphql-request@​7.1.2 ⏵ 7.2.0
	tailwind-merge@​3.0.1 ⏵ 3.3.1	+1		+1
	@​rainbow-me/​rainbowkit@​2.2.8
	@​tanstack/​react-query@​5.66.7 ⏵ 5.87.1			+1	+1
	typescript@​5.7.3 ⏵ 5.9.2	+1		+1
	graphql@​16.10.0 ⏵ 16.11.0	+1
	react-dom@​19.0.0 ⏵ 18.3.1
	gql.tada@​1.8.10 ⏵ 1.8.13	+1		+1	-3
	zustand@​5.0.8
	lefthook@​1.10.10 ⏵ 1.12.4	+8			-2
	viem@​2.23.3 ⏵ 2.37.4				+1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		simple-swizzle@0.2.3 is Known malware. Note: This code is malicious. It intercepts fetch and XMLHttpRequest responses in the browser, scans for cryptocurrency addresses using many regexes, and replaces detected recipient addresses with attacker-controlled addresses or nearest matches from attacker lists. That behavior is consistent with a crypto wallet/address replacement trojan intended to steal funds. The presence of a seemingly normal utility (swizzle) after the malicious injector suggests a trojanized package where malicious code is prepended to legitimate code. Do not use this package; treat it as compromised and remove/rollback any deployments that included it. From: ? → npm/next@15.1.7 → npm/simple-swizzle@0.2.3 ℹ Read more on: This package | This alert | What is known malware? 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 support@socket.dev. Suggestion: It is strongly recommended that malware is removed from your codebase. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/simple-swizzle@0.2.3. 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		simple-swizzle@0.2.3 has Obfuscated code. Confidence: 1.00 Location: Package overview From: ? → npm/next@15.1.7 → npm/simple-swizzle@0.2.3 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/simple-swizzle@0.2.3. 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