Update dependency eslint-plugin-react to v7.37.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-react	7.37.2 -> 7.37.5

---

Release Notes

jsx-eslint/eslint-plugin-react (eslint-plugin-react)

v7.37.5

Compare Source

Fixed

• [no-unknown-property]: allow shadow root attrs on <template> (#​3912 @​ljharb)
• [prop-types]: support ComponentPropsWithRef from a namespace import (#​3651 @​corydeppen)
• [jsx-no-constructed-context-values]: detect constructed context values in React 19 <Context> usage (#​3910 @​TildaDares)
• [no-unknown-property]: allow transform-origin on rect (#​3914 @​ljharb)

Changed

• [Docs] [button-has-type]: clean up phrasing (#​3909 @​hamirmahal)

v7.37.4

Compare Source

Fixed

• [no-unknown-property]: support onBeforeToggle, popoverTarget, popoverTargetAction attributes (#​3865 @​acusti)
• [types] fix types of flat configs (#​3874 @​ljharb)

v7.37.3

Compare Source

Fixed

• [no-danger]: avoid a crash on a nested component name (#​3833 @​ljharb)
• [Fix] types: correct generated type declaration (#​3840 @​ocavue)
• [no-unknown-property]: support precedence prop in react 19 (#​3829 @​acusti)
• [prop-types]: props missing in validation when using generic types from a namespace import (#​3859 @​rbondoc96)

Changed

• [Tests] [jsx-no-script-url]: Improve tests (#​3849 @​radu2147)
• [Docs] fix broken links: [default-props-match-prop-types], [jsx-boolean-value], [jsx-curly-brace-presence], [jsx-no-bind], [no-array-index-key], [no-is-mounted], [no-render-return-value], [require-default-props] (#​3841 @​bastiendmt)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: javascript/leap/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.16.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   3 more (eslint-plugin-import, eslint-plugin-jsx-a11y, eslint-plugin-react)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
npm error node_modules/eslint-config-airbnb
npm error   dev eslint-config-airbnb@"19.0.4" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
npm error   node_modules/eslint-config-airbnb
npm error     dev eslint-config-airbnb@"19.0.4" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-04-03T21_55_42_605Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-03T21_55_42_605Z-debug-0.log

File name: javascript/hello-world/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"9.16.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   3 more (eslint-plugin-import, eslint-plugin-jsx-a11y, eslint-plugin-react)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
npm error node_modules/eslint-config-airbnb
npm error   dev eslint-config-airbnb@"19.0.4" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
npm error   node_modules/eslint-config-airbnb
npm error     dev eslint-config-airbnb@"19.0.4" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-04-03T21_55_45_132Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-03T21_55_45_132Z-debug-0.log

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, eval	+21	749 kB	ljharb
npm/[email protected]	Transitive: eval	+85	9.82 MB	ljharb
npm/[email protected]	filesystem Transitive: environment, eval	+105	6.15 MB	ljharb
npm/[email protected]	None	0	7 kB	yeikos

🚮 Removed packages: npm/@babel/[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], npm/[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], npm/[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], npm/[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], npm/[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↗︎

[socket-security]

🚨 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	Note	Source	CI
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	javascript/hello-world/package-lock.json javascript/hello-world/package.json	🚫
Environment variable access	npm/[email protected]	Location: Package overview	javascript/hello-world/package-lock.json javascript/hello-world/package.json	🚫
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	javascript/hello-world/package-lock.json javascript/hello-world/package.json	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	javascript/hello-world/package-lock.json javascript/hello-world/package.json	🚫
Shell access	npm/[email protected]	Module: child_process Location: Package overview	javascript/hello-world/package-lock.json javascript/hello-world/package.json	🚫
Uses eval	npm/[email protected]	Eval Type: Function Location: Package overview	javascript/hello-world/package-lock.json javascript/hello-world/package.json	🚫
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	javascript/hello-world/package-lock.json javascript/hello-world/package.json	🚫
High CVE	npm/[email protected]	CVE: GHSA-c2qf-rxjj-qqgw semver vulnerable to Regular Expression Denial of Service (HIGH) Affected versions: < 5.7.2 Patched version: 5.7.2	javascript/hello-world/package-lock.json javascript/hello-world/package.json	🚫

View full report↗︎

Next steps

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is dynamic code execution?

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity 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

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]