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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merger #216

Open
wants to merge 35 commits into
base: main
Choose a base branch
from
Open

Merger #216

wants to merge 35 commits into from

Conversation

macide213
Copy link

Merge

Copy link

socket-security bot commented Nov 12, 2024

Copy link

socket-security bot commented Nov 12, 2024

🚨 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
Critical CVE npm/json-schema@0.2.3 ⚠︎
Critical CVE npm/loader-utils@0.2.17 ⚠︎
Critical CVE npm/eventsource@0.1.6 ⚠︎
Critical CVE npm/growl@1.9.2 ⚠︎
Critical CVE npm/https-proxy-agent@1.0.0 ⚠︎
Critical CVE npm/loader-utils@1.4.0 ⚠︎

View full report↗︎

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.

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/json-schema@0.2.3
  • @SocketSecurity ignore npm/loader-utils@0.2.17
  • @SocketSecurity ignore npm/eventsource@0.1.6
  • @SocketSecurity ignore npm/growl@1.9.2
  • @SocketSecurity ignore npm/https-proxy-agent@1.0.0
  • @SocketSecurity ignore npm/loader-utils@1.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant