@vitest/browser (npm) has 5 known vulnerabilities, the worst rated CRITICAL. Upgrade to 5.0.5 or later to clear all of them. No malicious-package signal is recorded.
Browser Mode exposes a set of built-in "commands" that run on the Node.js side of the test runner and can touch the local filesystem (taking screenshots…
CyberXYZ does not call a package safe in absolute terms. It records 5 known vulnerabilities for @vitest/browser (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does @vitest/browser have known vulnerabilities?
Yes. CyberXYZ records 5 known vulnerabilities for @vitest/browser (npm), the worst rated CRITICAL. They are GHSA-p63j-vcc4-9vmv, GHSA-g8mr-85jm-7xhm, GHSA-2h32-95rg-cppp, GHSA-p458-7748-mcp3, GHSA-8gvc-j273-4wm5.
Which version of @vitest/browser should I use?
5.0.5 or later clears every advisory recorded for @vitest/browser (npm). Check the release you pick before installing it.
How do I check @vitest/browser before installing?
Search @vitest/browser in CyberXYZ Check at https://cyberxyz.io/check?q=%40vitest%2Fbrowser. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:21 UTC. The most recent advisory here was published 2026-10-21. Updated continuously from NVD, GHSA, OSV and CNA feeds.