[Snyk] Security upgrade @vitest/coverage-istanbul from 3.1.1 to 4.0.0

[Dustin4444]

Snyk has created this PR to fix 2 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Command Injection SNYK-JS-GLOB-14040952	237
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BRACEEXPANSION-9789073	57

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Command Injection

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
v0-open-in-v0-0w	Error		Feb 10, 2026 0:58am

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-b1f72d32883c85ebed6217685591adcc

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @Dustin4444, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, aims to enhance the project's security by upgrading a development dependency. The upgrade specifically targets and resolves two identified vulnerabilities, improving the overall integrity of the codebase. A manual update to the pnpm-lock.yaml file is necessary to complete the changes.

Highlights

• Dependency Upgrade: Upgraded the @vitest/coverage-istanbul development dependency from version 3.1.1 to 4.0.0 in package.json.
• Security Vulnerability Fixes: Addressed two security vulnerabilities: a high-severity Command Injection (SNYK-JS-GLOB-14040952) and a low-severity Regular Expression Denial of Service (ReDoS) (SNYK-JS-BRACEEXPANSION-9789073).
• Manual pnpm-lock.yaml Update Required: A warning indicates that pnpm-lock.yaml could not be automatically updated and requires manual intervention before merging.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• package.json
  • Updated the version of @vitest/coverage-istanbul to ^4.0.0.

Activity

• This pull request was automatically created by Snyk to address identified security vulnerabilities.
• Snyk reported that the pnpm-lock.yaml file could not be updated automatically and requires manual resolution.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This PR from Snyk upgrades @vitest/coverage-istanbul from version 3.1.1 to 4.0.0 to resolve two security vulnerabilities. While this is an important security fix, there are a couple of critical points to address before merging. First, as noted in the PR description, the pnpm-lock.yaml file has not been updated. You must run pnpm install to regenerate the lockfile to ensure the updated dependency is used. Second, this is a major version upgrade (3.x to 4.x), which carries a risk of breaking changes. Given that vitest remains on version ^3.1.1, there's a potential for incompatibility. Please ensure thorough testing is performed to confirm that test coverage functionality is not broken by this upgrade.

[gemini-code-assist]

This major version upgrade of @vitest/coverage-istanbul from v3 to v4 could introduce breaking changes, as indicated by Snyk (isBreakingChange:true). The vitest package in your project is at version ^3.1.1, which might be incompatible with this new version of the coverage plugin. Please verify compatibility and test thoroughly to ensure test coverage reporting still works as expected. You may need to upgrade vitest and other related dependencies as well.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​typescript-eslint/​utils@​8.18.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		Network access: npm @typescript-eslint/typescript-estree in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: pnpm-lock.yaml → npm/@typescript-eslint/parser@8.18.1 → npm/@typescript-eslint/utils@8.18.1 → npm/@typescript-eslint/rule-tester@8.18.1 → npm/@eslint-react/eslint-plugin@1.21.0 → npm/@typescript-eslint/typescript-estree@8.18.1 ℹ Read more on: This package | This alert | What is network access? 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/typescript-estree@8.18.1. 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		Network access: npm @typescript-eslint/utils in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: packages/eslint-plugin-query/package.json → npm/@typescript-eslint/utils@8.18.1 ℹ Read more on: This package | This alert | What is network access? 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/utils@8.18.1. 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		Network access: npm @urql/core in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: pnpm-lock.yaml → npm/@urql/core@5.0.8 ℹ Read more on: This package | This alert | What is network access? 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 remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@urql/core@5.0.8. 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		Embedded URLs or IPs: npm @typescript-eslint/types with es2017.date, es2020.date URLs: es2017.date, es2020.date Location: Package overview From: pnpm-lock.yaml → npm/@typescript-eslint/parser@8.18.1 → npm/@typescript-eslint/utils@8.18.1 → npm/@typescript-eslint/rule-tester@8.18.1 → npm/@eslint-react/eslint-plugin@1.21.0 → npm/@typescript-eslint/types@8.18.1 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/types@8.18.1. 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		Embedded URLs or IPs: npm @typescript-eslint/typescript-estree URLs: https://typescript-eslint.io/troubleshooting/typed-linting#are-typescript-project-references-supported, https://typescript-eslint.io/troubleshooting/typed-linting#i-get-errors-telling-me-eslint-was-configured-to-run--however-that-tsconfig-does-not--none-of-those-tsconfigs-include-this-file, https://typescript-eslint.io/troubleshooting/faqs/general#the-key-property-is-deprecated-on-type-nodes-use-key-instead-warnings., this.foo, https://typescript-eslint.io/troubleshooting/typed-linting#allowdefaultproject-glob-too-wide, https://github.com/typescript-eslint/typescript-eslint/issues/101., https://github.com/typescript-eslint/typescript-eslint/issues/6289, https://github.com/typescript-eslint/typescript-eslint/issues/9905, https://github.com/typescript-eslint/typescript-eslint/issues/7896 Location: Package overview From: pnpm-lock.yaml → npm/@typescript-eslint/parser@8.18.1 → npm/@typescript-eslint/utils@8.18.1 → npm/@typescript-eslint/rule-tester@8.18.1 → npm/@eslint-react/eslint-plugin@1.21.0 → npm/@typescript-eslint/typescript-estree@8.18.1 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/typescript-estree@8.18.1. 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		Embedded URLs or IPs: npm @typescript-eslint/utils URLs: https://github.com/eslint/espree, http://json-schema.org/schema#, http://json-schema.org/hyper-schema#, http://json-schema.org/draft-04/schema#, http://json-schema.org/draft-04/hyper-schema#, http://json-schema.org/draft-03/schema#, http://json-schema.org/draft-03/hyper-schema#, https://tools.ietf.org/html/draft-zyp-json-schema-03#section-5.3, https://tools.ietf.org/html/draft-zyp-json-schema-03#section-5.2, https://json-schema.org/understanding-json-schema/reference/array.html, https://tools.ietf.org/html/draft-zyp-json-schema-03#section-5.6, https://tools.ietf.org/html/draft-zyp-json-schema-03#section-5.5, https://json-schema.org/understanding-json-schema/reference/string.html, https://json-schema.org/understanding-json-schema/reference/numeric.html, https://tools.ietf.org/html/draft-zyp-json-schema-03#section-5.19, https://json-schema.org/understanding-json-schema/reference/boolean.html, https://json-schema.org/understanding-json-schema/reference/null.html, https://eslint-community.github.io/eslint-utils/api/ast-utils.html#getstringifconstant, https://eslint-community.github.io/eslint-utils/api/ast-utils.html#hassideeffect, https://typescript-eslint.io/getting-started/typed-linting, https://eslint.org/docs/developer-guide/working-with-rules#messageids Location: Package overview From: packages/eslint-plugin-query/package.json → npm/@typescript-eslint/utils@8.18.1 ℹ Read more on: This package | This alert | What are URL strings? 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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/utils@8.18.1. 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		Environment variable access: npm @urql/core reads NODE_ENV Env Vars: NODE_ENV Location: Package overview From: pnpm-lock.yaml → npm/@urql/core@5.0.8 ℹ Read more on: This package | This alert | What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@urql/core@5.0.8. 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		Environment variable access: npm @urql/exchange-retry reads NODE_ENV Env Vars: NODE_ENV Location: Package overview From: pnpm-lock.yaml → npm/@urql/exchange-retry@1.3.0 ℹ Read more on: This package | This alert | What is environment variable access? 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 be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@urql/exchange-retry@1.3.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