Skip to content

Add missing peer dependency

0d13813
Select commit
Loading
Failed to load commit list.
Merged

Migrate to Vitest #260

Add missing peer dependency
0d13813
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed Mar 24, 2025 in 14s

Pull Request #260 Alerts: Complete with warnings

Report Status Message
PR #260 Alerts ⚠️ Found 5 project alerts

Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.

Details

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Network access npm/vite@6.2.0 🚫
Network access npm/vite@6.2.0 🚫
Shell access npm/vite@6.2.0 🚫
Network access npm/vite@6.2.0 🚫
Network access npm/vite@6.2.0 🚫

Ignoring: npm/tinypool@1.0.2, npm/tinyexec@0.3.2, npm/esbuild@0.25.0, npm/istanbul-lib-report@3.0.1

View full report↗︎

Next steps

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/vite@6.2.0