chore: update vitest

[rossgalloway]

Description

• Update vitest to version 4. Should resolve this alert: https://github.com/yearn/yearn.fi/security/dependabot/34
• Makes changes to some tests that required DOM access and would require a new jsdom dependency.

Related Issue

This clears a bunch of other vitest update PRs:

• chore(deps-dev): bump vitest from 1.6.1 to 3.2.6 #1273
• chore(deps-dev): bump vitest from 1.6.1 to 4.0.18 #1032
• Chore: bump vitest to 4.0.6 #826

Motivation and Context

cleanup and security

How Has This Been Tested?

ran test runner locally. site builds and preview displays fine.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
yearnfi	Ready	Preview, Comment	Jun 9, 2026 1:48pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
yearnfi-nextjs	Ignored	Preview	Jun 9, 2026 1:48pm
yearnfi-nextjs-2	Ignored	Preview	Jun 9, 2026 1:48pm

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/vitest	4.1.8	Unknown	Unknown

Scanned Files

• package.json

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	vitest@​1.6.1 ⏵ 4.1.8	+1	+75	+1

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		Obfuscated code: npm @internationalized/date is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@headlessui/react@2.2.10 → npm/@internationalized/date@3.12.2 ℹ 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/@internationalized/date@3.12.2. 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		Obfuscated code: npm react-stately is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/@headlessui/react@2.2.10 → npm/react-stately@3.47.0 ℹ 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/react-stately@3.47.0. 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

[rossgalloway]

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
Obfuscated code: npm @internationalized/date is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ? → npm/@headlessui/react@2.2.10 → npm/@internationalized/date@3.12.2

ℹ 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/@internationalized/date@3.12.2`. 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](https://socket.dev/dashboard/org/yearn/diff-scan/57544210-e874-49d4-a979-917e1b4ffd27/alert/QQnUUoKoWUOKvz7A6VyneBYLZ4CuTmOIt-U17Bfrnccs).

Warn
Obfuscated code: npm react-stately is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: ? → npm/@headlessui/react@2.2.10 → npm/react-stately@3.47.0

ℹ 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/react-stately@3.47.0`. 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](https://socket.dev/dashboard/org/yearn/diff-scan/57544210-e874-49d4-a979-917e1b4ffd27/alert/QO-QOEXj-i8Yt5_BrL-nvGqxp6DBtQoRxVaCpBy9kEYc).

View full report

Both the libraries with "obfuscated code" seem legit and are published by Adobe. To remove these, I think we would need to change out the headless-react library for another component library.