Skip to content

feat: migrate from ESLint v8 to ESLint v9 flat config #5825

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.

Sign up for GitHub

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

Draft
fengmk2 wants to merge 1 commit into
base: 3.x
Choose a base branch
from

feat: migrate from ESLint v8 to ESLint v9 flat config

645c824
Select commit
Loading
Failed to load commit list.
Draft

feat: migrate from ESLint v8 to ESLint v9 flat config #5825

feat: migrate from ESLint v8 to ESLint v9 flat config
645c824
Select commit
Loading
Failed to load commit list.
Socket Security / Socket Security: Pull Request Alerts completed Mar 8, 2026 in 41s

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

Report Status Message
PR #5825 Alerts ⚠️ Found 2 project alerts

Pull request alerts notify when new issues are detected between the diff of the pull request and it's target branch.

Details

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Critical
Critical CVE: Prototype Pollution in npm immer

CVE: GHSA-33f9-j839-rf8h Prototype Pollution in immer (CRITICAL)

Affected versions: >= 7.0.0 < 9.0.6

Patched version: 9.0.6

From: ? → npm/@umijs/preset-react@2.1.7 → npm/immer@8.0.4

ℹ Read more on: This package | This alert | What is a critical CVE?

Next steps: 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@socket.dev.

Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/immer@8.0.4. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn Critical
Potential typosquat: npm slash2 as a typo of slash

Did you mean: slash2

From: ? → npm/dumi@1.1.54 → npm/dumi-theme-egg@1.2.4 → npm/slash2@2.0.0

ℹ Read more on: This package | This alert | What is a typosquat?

Next steps: 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@socket.dev.

Suggestion: Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/slash2@2.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

View more details on Socket Security