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

feat: drop ESLint v2, v3, v4, v5, v6 & v7 support #3092

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

MichaelDeBoey
Copy link

BREAKING CHANGE: Requires ESLint@^8.57.0 || ^9.0.0

BREAKING CHANGE: Requires Node@^18.18.0 || ^20.9.0 || >=21.1.0
BREAKING CHANGE: Requires ESLint@^8.57.0 || ^9.0.0
@MichaelDeBoey MichaelDeBoey force-pushed the drop-ESLint-2-3-4-5-6-7-support branch from 3eec871 to a240113 Compare October 29, 2024 14:15
Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] Transitive: environment, eval, filesystem +5 2.34 MB loganfsmyth
npm/[email protected] environment, filesystem Transitive: eval, unsafe +11 4.68 MB hzoo
npm/[email protected] None 0 282 kB hzoo
npm/[email protected] None +7 910 kB chaijs
npm/[email protected] environment Transitive: filesystem, shell +7 95.3 kB kentcdodds
npm/[email protected] Transitive: environment, eval, filesystem, unsafe +67 7.04 MB bmishkin
npm/[email protected] Transitive: environment, filesystem +1 150 kB bradzacher
npm/[email protected] filesystem 0 105 kB not-an-aardvark
npm/[email protected] None 0 1.35 MB benmosher, jfmengels, ljharb
npm/[email protected] None +2 1.9 MB abandeali
npm/[email protected] filesystem 0 8.57 kB coderaiser
npm/[email protected] None 0 4.01 kB iarna
npm/[email protected] filesystem Transitive: shell +6 341 kB timoxley
npm/[email protected] Transitive: environment, filesystem, shell +22 3.69 MB davidanson
npm/[email protected] environment Transitive: filesystem, shell +2 88.8 kB timoxley
npm/[email protected] environment +3 1.57 MB timdorr
npm/[email protected] filesystem 0 15.5 kB isaacs
npm/[email protected] environment, shell 0 19 kB ljharb
npm/[email protected] None +2 6.7 MB mrgnrdrck
npm/[email protected] None +1 139 kB eslint
npm/[email protected] None 0 64 MB typescript-bot

🚮 Removed packages: npm/@typescript-eslint/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

Copy link

🚨 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/[email protected] ⚠︎

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

jaguiarjardim-riparian
jaguiarjardim-riparian approved these changes Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants