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

[Snyk] Security upgrade eslint from 4.18.2 to 9.15.0 #243

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

fix: assets/package.json to reduce vulnerabilities

311392d
Select commit
Loading
Failed to load commit list.
Open

[Snyk] Security upgrade eslint from 4.18.2 to 9.15.0 #243

fix: assets/package.json to reduce vulnerabilities
311392d
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts failed Nov 16, 2024 in 1m 20s

Pull Request #243 Alerts: Complete with warnings WARNING: Free tier size exceeded

Report Status Message
PR #243 Alerts ⚠️ Found 7 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 NoteSourceCI
Critical CVE npm/json-schema@0.2.3 ⚠︎
Critical CVE npm/loader-utils@0.2.17 ⚠︎
Known malware npm/fsevents@1.1.2
  • Note: This package downloads prebuilt artifacts from a domain which has been compromised. Your system may be infected if you installed this package prior to April 27, 2023
🚫
Critical CVE npm/fsevents@1.1.2 ⚠︎
Critical CVE npm/deep-extend@0.4.2 ⚠︎
Critical CVE npm/babel-traverse@6.25.0 ⚠︎
Critical CVE npm/deap@1.0.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.

What is known malware?

This package is malware. We have asked the package registry to remove it.

It is strongly recommended that malware is removed from your codebase.

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/fsevents@1.1.2
  • @SocketSecurity ignore npm/deep-extend@0.4.2
  • @SocketSecurity ignore npm/babel-traverse@6.25.0
  • @SocketSecurity ignore npm/deap@1.0.0