[Snyk] Security upgrade chokidar from 2.1.8 to 3.0.0 #9
Pull Request #9 Alerts: Complete with warnings WARNING: Free tier size exceeded
| Report | Status | Message |
|---|---|---|
| PR #9 Alerts | Found 8 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 | Note | Source |
|---|---|---|---|
| Telemetry | npm/nightwatch@2.3.9 |
| |
| Install scripts | npm/fsevents@1.2.13 |
| |
| Install scripts | npm/node-pty@0.10.1 |
| |
| Install scripts | npm/node-pty@0.10.1 |
| |
| Install scripts | npm/@vscode/ripgrep@1.15.6 |
| |
| Install scripts | npm/web3@1.10.3 |
| |
| Install scripts | npm/yarn@1.22.21 |
| |
| Install scripts | npm/electron@25.9.5 |
|
Next steps
What is telemetry?
This package contains telemetry which tracks how it is used.
Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.
What is an install script?
Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.
Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.
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/nightwatch@2.3.9@SocketSecurity ignore npm/fsevents@1.2.13@SocketSecurity ignore npm/node-pty@0.10.1@SocketSecurity ignore npm/@vscode/ripgrep@1.15.6@SocketSecurity ignore npm/web3@1.10.3@SocketSecurity ignore npm/yarn@1.22.21@SocketSecurity ignore npm/electron@25.9.5