build(deps-dev): bump vitest and @vitest/coverage-v8 #136
Pull Request #136 Alerts: Complete with warnings
| Report | Status | Message |
|---|---|---|
| PR #136 Alerts | Found 115 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.
Next steps
What is a chronological version anomaly?
Semantic versions published out of chronological order.
This could either indicate dependency confusion or a patched vulnerability.
What is dynamic require?
Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.
What is environment variable access?
Package accesses environment variables, which may be a sign of credential stuffing or data theft.
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.
What is filesystem access?
Accesses the file system, and could potentially read sensitive data.
If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.
What is a mixed license?
(Experimental) Package contains multiple licenses.
A new version of the package should be published that includes a single license. Consumers may seek clarification from the package author. Ensure that the license details are consistent across the LICENSE file, package.json license field and license details mentioned in the README.
What is eval?
Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.
Avoid packages that use eval, since this could potentially execute any code.
What is an empty package?
Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.
Remove dependencies that do not export any code or functionality and ensure the package version includes all of the files it is supposed to.
What is a major refactor?
Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Consider waiting before upgrading to see if any issues are discovered, or be prepared to scrutinize any bugs or subtle changes the major refactor may bring. Publishers my consider publishing beta versions of major refactors to limit disruption to parties interested in the new changes.
What is wrong with semver < v1?
Package is not semver >=1. This means it is not stable and does not support ^ ranges.
If the package sees any general use, it should begin releasing at version 1.0.0 or later to benefit from semver.
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 package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @rollup/[email protected]@SocketSecurity ignore @babel/[email protected]@SocketSecurity ignore [email protected]@SocketSecurity ignore [email protected]