Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Fix for 1 vulnerabilities #436

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

fix: package.json & yarn.lock to reduce vulnerabilities

32f5721
Select commit
Failed to load commit list.
Open

[Snyk] Fix for 1 vulnerabilities #436

fix: package.json & yarn.lock to reduce vulnerabilities
32f5721
Select commit
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed Jun 20, 2023 in 10m 23s

Pull Request #436 Alerts: Complete with warnings

Report Status Message
PR #436 Alerts 鈿狅笍 Found 14 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.

Issue Package Version Note Source
Network access http2-wrapper 2.2.0 package.json via update-notifier@6.0.2
Network access resolve-alpn 1.2.1 package.json via update-notifier@6.0.2

Next steps

What is network access?

This module accesses the network.

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

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 foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore http2-wrapper@2.2.0
  • @SocketSecurity ignore resolve-alpn@1.2.1