[Snyk] Fix for 2 vulnerabilities #1050
Pull Request #1050 Alerts: Complete with warnings WARNING: Free tier size exceeded
| Report | Status | Message |
|---|---|---|
| PR #1050 Alerts | Found 6 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 | CI |
|---|---|---|---|---|
| Critical CVE | npm/[email protected] |
| ⚠︎ | |
| Critical CVE | npm/[email protected] |
| ⚠︎ | |
| Critical CVE | npm/[email protected] |
| ⚠︎ | |
| Git dependency | npm/[email protected] |
| ⚠︎ | |
| Protestware or potentially unwanted behavior | npm/[email protected] |
| ⚠︎ | |
| Protestware or potentially unwanted behavior | npm/[email protected] |
| ⚠︎ |
Next steps
What is a critical CVE?
Contains a Critical Common Vulnerability and Exposure (CVE).
Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.
What are git dependencies?
Contains a dependency which resolves to a remote git URL. Dependencies fetched from git URLs are not immutable can be used to inject untrusted code or reduce the likelihood of a reproducible install.
Publish the git dependency to npm or a private package repository and consume it from there.
What is protestware?
This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.
Consider that consuming this package may come along with functionality unrelated to its primary purpose.
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/[email protected] or ignore all packages with @SocketSecurity ignore-all
@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]@SocketSecurity ignore npm/[email protected]