Skip to content

Bump eslint-plugin-react-hooks from 4.6.2 to 7.1.1#76

Open
dependabot[bot] wants to merge 2 commits intomainfrom
dependabot/npm_and_yarn/eslint-plugin-react-hooks-7.1.1
Open

Bump eslint-plugin-react-hooks from 4.6.2 to 7.1.1#76
dependabot[bot] wants to merge 2 commits intomainfrom
dependabot/npm_and_yarn/eslint-plugin-react-hooks-7.1.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 4, 2026 •
edited
Loading

Bumps eslint-plugin-react-hooks from 4.6.2 to 7.1.1.

Release notes

Sourced from eslint-plugin-react-hooks's releases.

eslint-plugin-react-hooks@7.1.1 (April 17, 2026)

Note: 7.1.0 accidentally removed the component-hook-factories rule, causing errors for users who referenced it in their ESLint config. This is now fixed.

  • Add deprecated no-op component-hook-factories rule for backwards compatibility. (@​mofeiZ in #36307)

eslint-plugin-react-hooks@7.1.0 (April 16, 2026)

This release adds ESLint v10 support, improves performance by skipping compilation for non-React files, and includes compiler lint improvements including better set-state-in-effect detection, improved ref validation, and more helpful error reporting.

eslint-plugin-react-hooks@5.0.0 (Oct 11, 2024)

This release only contains eslint-plugin-react-hooks. Notably, new violations and support for ESLint v9 were added.

eslint-plugin-react-hooks

  • New Violations: Component names now need to start with an uppercase letter instead of a non-lowercase letter. This means _Button or _component are no longer valid. (@​kassens) in #25162 For example, in 
    function _Component() {
  useState()
  ^^^^^^^^ A React Hook "useState" is called in function "_Component" which is neither a Component nor a custom React Hook function.
}
    _Component should be renamed to Component.
Changelog

Sourced from eslint-plugin-react-hooks's changelog.

7.1.1

Note: 7.1.0 accidentally removed the component-hook-factories rule, causing errors for users who referenced it in their ESLint config. This is now fixed.

  • Add deprecated no-op component-hook-factories rule for backwards compatibility. (@​mofeiZ in #36307)

7.1.0

This release adds ESLint v10 support, improves performance by skipping compilation for non-React files, and includes compiler lint improvements including better set-state-in-effect detection, improved ref validation, and more helpful error reporting.

7.0.1

  • Disallowed passing inline useEffectEvent values as JSX props to guard against accidental propagation. (#34820 by @​jf-eirinha)
  • Switch to export = so eslint-plugin-react-hooks emits correct types for consumers in Node16 ESM projects. (#34949 by @​karlhorky)
  • Tightened the typing of configs.flat so the configs export is always defined. (#34950 by @​poteto)
  • Fix named import runtime errors. (#34951, #34953 by @​karlhorky)

7.0.0

This release slims down presets to just 2 configurations (recommended and recommended-latest), and all compiler rules are enabled by default.

  • Breaking: Removed recommended-latest-legacy and flat/recommended configs. The plugin now provides recommended (legacy and flat configs with all recommended rules), and recommended-latest (legacy and flat configs with all recommended rules plus new bleeding edge experimental compiler rules). (@​poteto in #34757)

6.1.1

Note: 6.1.0 accidentally allowed use of recommended without flat config, causing errors when used with ESLint v9's defineConfig() helper. This has been fixed in 6.1.1.

6.1.0

Note: Version 6.0.0 was mistakenly released and immediately deprecated and untagged on npm. This is the first official 6.x major release and includes breaking changes.

... (truncated)

Commits

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 4, 2026

Labels

The following labels could not be found: dependencies, npm. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 4, 2026 •
edited
Loading

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updatedeslint-plugin-react-hooks@​4.6.2 ⏵ 7.1.1100 +1100100 +896100

View full report

@socket-security
Copy link
Copy Markdown

socket-security Bot commented May 4, 2026 •
edited
Loading

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block Low
Filesystem access: npm hermes-parser with module fs

Module: fs

Location: Package overview

From: package-lock.json → npm/eslint-plugin-react-hooks@7.1.1 → npm/hermes-parser@0.25.1

ℹ Read more on: This package | This alert | What is filesystem access?

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: 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.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/hermes-parser@0.25.1. 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.

Block Low
Minified code present: npm hermes-parser with 100.0% likelihood

Confidence: 1.00

Location: Package overview

From: package-lock.json → npm/eslint-plugin-react-hooks@7.1.1 → npm/hermes-parser@0.25.1

ℹ Read more on: This package | This alert | What's wrong with minified code?

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: In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/hermes-parser@0.25.1. 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.

Block Low
Embedded URLs or IPs: npm hermes-parser

URLs: https://github.com/eslint/eslint/blob/21d647904dc30f9484b22acdd9243a6d0ecfba38/lib/linter/linter.js#L779, https://github.com/prettier/prettier/issues/11793

Location: Package overview

From: package-lock.json → npm/eslint-plugin-react-hooks@7.1.1 → npm/hermes-parser@0.25.1

ℹ Read more on: This package | This alert | What are URL strings?

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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/hermes-parser@0.25.1. 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.

Block Low
Potential code anomaly (AI signal): npm zod is 100.0% likely to have a medium risk anomaly

Notes: No explicit network exfiltration, reverse shell, or credential theft is present in this fragment. However, the code assembles and compiles arbitrary code via the Function constructor and invokes passed-in functions immediately (twice). That behavior constitutes a strong dangerous primitive (arbitrary code execution) which can be abused if any inputs (strings or args) are attacker-controlled. Treat this module as risky in threat models where inputs are not fully trusted; review call sites and sanitize/validate inputs or avoid dynamic evaluation.

Confidence: 1.00

Severity: 0.60

From: package-lock.json → npm/eslint-plugin-react-hooks@7.1.1 → npm/zod@4.4.3

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

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: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/zod@4.4.3. 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.

Block Low
Minified code present: npm zod with 95.0% likelihood

Confidence: 0.95

Location: Package overview

From: package-lock.json → npm/eslint-plugin-react-hooks@7.1.1 → npm/zod@4.4.3

ℹ Read more on: This package | This alert | What's wrong with minified code?

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: In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/zod@4.4.3. 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.

Block Low
Embedded URLs or IPs: npm zod

URLs: 127.0.0.1, z.date, lkajsdf.com, gmail.com, https://json-schema.org/draft/2020-12/schema, http://json-schema.org/draft-07/schema#, http://json-schema.org/draft-04/schema#, domain.com, firstname.lastname@domain.com, subdomain.domain.com, domain-one.com, domain.name, domain.co.jp, very.common@example.com, disposable.style.email.with+symbol@example.com, other.email-with-hyphen@example.com, example.com, user.name+tag+sorting@example.com, asdf.example.com, strange-example.com, example.org, my-example.com, b.cd, mail.com, test.te-st.com, etu.inp-n7.fr, example.com@example.org, test.com, strange.example.com, 123.123.123.123, email.domain.com, -domain.com, Abc.example.com, but_its_not_allowed_in_this_part.example.com, -start.com, http://google.com, https://google.com/asdf?asdf=ljk3lk4&asdf=234#asdf, lkjsdf.com, 122.122.122.122, 254.164.77.1, 114.71.82.94, 0.0.0.0, 37.85.236.115, 192.168.0.1/24, 192.168.0.0/24, 10.0.0.0/8, 203.0.113.0/24, 192.0.2.0/24, 127.0.0.0/8, 172.16.0.0/12, 192.168.1.0/24, 192.168.1.1/33, 10.0.0.1/-1, 192.168.1.1/24/24, 192.168.1.0/abc, https://stackoverflow.com/a/46181/1550155, https://thekevinscott.com/emojis-in-javascript/#writing-a-regular-expression, https://stackoverflow.com/questions/7860392/determine-if-string-is-in-base64-using-javascript, https://base64.guru/standards/base64url, https://stackoverflow.com/a/3143231, https://stackoverflow.com/questions/3966484/why-does-modulus-operator-return-fractional-number-in-javascript/31711034#31711034, https://example.com/path?query=value, https://test.com/api/v1?foo=bar&baz=qux, https://example.com/path, http://example.com/path, http://api.example.com/v1/users, ftp://example.com, https://example.com/schema#/definitions/User, https://example.com/schemas/user, z.coerce.date, z.iso.date, z.map, https://github.com/colinhacks/zod/security/advisories/GHSA-r34p-xfmx-58wv, https://github.com/colinhacks/zod/security/advisories/GHSA-84jv-fqfx-wxhr, user.name, http://example.org/, https://my.local, https://example.com?key=NUXOmHqWNVTapJkJJHw8BfD155AuqhH_qju_5fNmQ4ZHV7u8, https://example.com?foo=bar, http://example.com?test=123, https://sub.example.com?param=value&other=data, https://example.com/, https://example.com/path/, https://example.com/path?query=param, https://example.com, https://example.com?key=value, https://example.com/?key=value, http://example.com/?test=123, https://example.com/../?key=value, https://example.com/./path?key=value, https://example.com/path?key=value, http://example.com?key=value, https://other.com?key=value, http://example.com, https://example.com:8080, http://example.com:8080, https://sub.example.com, http://sub.example.com, https://example.com/path/to/resource, http://example.com/path/to/resource, http://example.com/path?query=param, https://example.com/path#fragment, http://example.com/path#fragment, shttp://example.com, httpz://example.com, http://-asdf.com, http://asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf.com, http://asdf.c, developer.mozilla.org/en-US/docs/Web/API/URL/password, lckj.com, www.google.com, 94.105.123.75, 192.168.0.1, 255.255.255.255, 1.2.3.4, 0.0.0.0/0, 255.255.255.255/32, 192.168.0.0, 192.168.0.0/33, 192.168.0.0/-1, sub.example.com, a-b-c.example.com, 123.example.com, example-123.com, developer.mozilla.org, hello.world.example.com, 192.168.1.1, xn--d1acj3b.com, xn--d1acj3b.org, example-.com, -example.com, example.com:8080, tp://invalid.com, mple.com, e.co, EXAMPLE.COM, https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/email, https://stackoverflow.com/questions/106179/regular-expression-to-match-dns-hostname-or-ip-address, https://blog.stevenlevithan.com/archives/validate-phone-number#r4-3, z.lt, z.gt, z.int, z.email, https://example.com/path?query=123#fragment, http://example.com/, http://example.com//, http://examples.com, http://example.org, https://example.org, 213.174.246.205, https://speedtest.net, https://example.net.il, https://github.com/paralleldrive/cuid., jsonSchema.id, https://example.com/Post.json, https://example.com/User.json

Location: Package overview

From: package-lock.json → npm/eslint-plugin-react-hooks@7.1.1 → npm/zod@4.4.3

ℹ Read more on: This package | This alert | What are URL strings?

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: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/zod@4.4.3. 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

@guibranco guibranco enabled auto-merge (squash) May 5, 2026 05:14
@gstraccini gstraccini Bot added the ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) label May 5, 2026
@gstraccini gstraccini Bot added the 🤖 bot Automated processes or integrations label May 5, 2026
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/eslint-plugin-react-hooks-7.1.1 branch from 9cd2c05 to d65287e Compare May 5, 2026 10:50
guibranco
guibranco approved these changes May 5, 2026
View reviewed changes
Copy link
Copy Markdown
Owner

@guibranco guibranco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automatically approved by gstraccini[bot]

@dependabot
Bump eslint-plugin-react-hooks from 4.6.2 to 7.1.1
cad515c 
Bumps [eslint-plugin-react-hooks](https://github.com/facebook/react/tree/HEAD/packages/eslint-plugin-react-hooks) from 4.6.2 to 7.1.1.
- [Release notes](https://github.com/facebook/react/releases)
- [Changelog](https://github.com/facebook/react/blob/main/packages/eslint-plugin-react-hooks/CHANGELOG.md)
- [Commits](https://github.com/facebook/react/commits/eslint-plugin-react-hooks@7.1.1/packages/eslint-plugin-react-hooks)

---
updated-dependencies:
- dependency-name: eslint-plugin-react-hooks
  dependency-version: 7.1.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/eslint-plugin-react-hooks-7.1.1 branch from d65287e to cad515c Compare May 5, 2026 17:52
@deepsource-io
Copy link
Copy Markdown

deepsource-io Bot commented May 6, 2026 •
edited
Loading

DeepSource Code Review

We reviewed changes in 860e9d9...5bdce59 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
JavaScript May 6, 2026 2:55p.m. Review ↗
Secrets May 6, 2026 2:55p.m. Review ↗

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@guibranco guibranco guibranco approved these changes

@gstraccini gstraccini[bot] gstraccini[bot] approved these changes

Assignees

@guibranco guibranco

Labels

☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) 🤖 bot Automated processes or integrations

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@guibranco