eslint-plugin-react
React specific linting rules for ESLint
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): ljharb is a highly reputable npm publisher (918 approved packages, 4617 days history). This is a documented legitimate maintainer transition for eslint-plugin-react. | ai | |
| source-diff | large-new-source-files | AI (source-diff): eslint-plugin-react regularly adds new lint rule files across versions; 22 new source files is consistent with normal feature development for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All 6 new deps (resolve, object.values, array-includes, object.entries, object.fromentries, string.prototype.matchall) are well-known legitimate utility packages, many maintained by ljharb himself. | ai | |
| provenance | publisher-changed | AI (provenance): ljharb is a well-known, highly reputable npm publisher who legitimately took over stewardship of eslint-plugin-react from yannickcr. This is a documented, benign maintainer transition. | ai | |
| dependencies | unvetted-dep:object.hasown | AI (dependencies): object.hasown is a standard ljharb-ecosystem polyfill; its use here is legitimate and consistent across versions of this package. | ai | |
| dependencies | unvetted-dep:array.prototype.toreversed | AI (dependencies): Polyfill dependency; consistent with package's design pattern of using array/string prototype polyfills. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to detect the installed React version via resolve.sync — a standard, safe pattern for ESLint plugins. Stable for this package. | ai |
Versions (showing 100 of 205)
| Version | Deps | Published |
|---|---|---|
| 7.5.0 | 4 / 5 | |
| 7.4.0 | 4 / 5 | |
| 7.3.0 | 4 / 5 | |
| 7.2.1 | 3 / 5 | |
| 7.2.0 | 3 / 5 | |
| 7.1.0 | 3 / 5 | |
| 7.0.1 | 3 / 5 | |
| 7.0.0 | 3 / 5 | |
| 6.10.3 | 5 / 5 | |
| 6.10.2 | 5 / 5 | |
| 6.10.1 | 5 / 5 | |
| 6.10.0 | 5 / 5 | |
| 6.9.0 | 3 / 5 | |
| 6.8.0 | 2 / 5 | |
| 6.7.1 | 2 / 5 | |
| 6.7.0 | 2 / 5 | |
| 6.6.0 | 2 / 5 | |
| 6.5.0 | 2 / 5 | |
| 6.4.1 | 2 / 5 | |
| 6.4.0 | 2 / 5 | |
| 6.3.0 | 2 / 5 | |
| 6.2.2 | 2 / 5 | |
| 6.2.1 | 2 / 5 | |
| 6.2.0 | 2 / 5 | |
| 6.1.2 | 2 / 5 | |
| 6.1.1 | 2 / 5 | |
| 6.1.0 | 2 / 5 | |
| 6.0.0 | 2 / 5 | |
| 5.2.2 | 2 / 5 | |
| 5.2.1 | 2 / 5 | |
| 5.2.0 | 2 / 5 | |
| 5.1.1 | 0 / 5 | |
| 5.1.0 | 0 / 5 | |
| 5.0.1 | 0 / 5 | |
| 5.0.0 | 0 / 5 | |
| 4.3.0 | 0 / 5 | |
| 4.2.3 | 0 / 5 | |
| 4.2.2 | 0 / 5 | |
| 4.2.1 | 0 / 5 | |
| 4.2.0 | 0 / 5 | |
| 4.1.0 | 0 / 5 | |
| 4.0.0 | 0 / 5 | |
| 3.16.1 | 0 / 5 | |
| 3.16.0 | 0 / 5 | |
| 3.15.0 | 0 / 5 | |
| 3.14.0 | 0 / 5 | |
| 3.13.1 | 0 / 5 | |
| 3.13.0 | 0 / 5 | |
| 3.12.0 | 0 / 5 | |
| 3.11.3 | 0 / 5 | |
| 3.11.2 | 0 / 5 | |
| 3.11.1 | 0 / 5 | |
| 3.11.0 | 0 / 5 | |
| 3.10.0 | 0 / 5 | |
| 3.9.0 | 0 / 5 | |
| 3.8.0 | 0 / 5 | |
| 3.7.1 | 0 / 5 | |
| 3.7.0 | 0 / 5 | |
| 3.6.3 | 0 / 5 | |
| 3.6.2 | 0 / 5 | |
| 3.6.1 | 0 / 5 | |
| 3.6.0 | 0 / 5 | |
| 3.5.1 | 0 / 5 | |
| 3.5.0 | 0 / 5 | |
| 3.4.2 | 0 / 5 | |
| 3.4.1 | 0 / 5 | |
| 3.4.0 | 0 / 5 | |
| 3.3.2 | 0 / 5 | |
| 3.3.1 | 0 / 5 | |
| 3.3.0 | 0 / 5 | |
| 3.2.3 | 0 / 5 | |
| 3.2.2 | 0 / 5 | |
| 3.2.1 | 0 / 5 | |
| 3.2.0 | 0 / 5 | |
| 3.1.0 | 0 / 5 | |
| 3.0.0 | 0 / 6 | |
| 2.7.1 | 0 / 6 | |
| 2.7.0 | 0 / 6 | |
| 2.6.4 | 0 / 6 | |
| 2.6.3 | 0 / 6 | |
| 2.6.2 | 0 / 6 | |
| 2.6.1 | 0 / 6 | |
| 2.6.0 | 0 / 6 | |
| 2.5.2 | 0 / 6 | |
| 2.5.1 | 0 / 6 | |
| 2.5.0 | 0 / 6 | |
| 2.4.0 | 0 / 6 | |
| 2.3.0 | 0 / 6 | |
| 2.2.0 | 0 / 6 | |
| 2.1.1 | 0 / 6 | |
| 2.1.0 | 0 / 5 | |
| 2.0.2 | 0 / 5 | |
| 2.0.1 | 0 / 5 | |
| 2.0.0 | 0 / 5 | |
| 1.6.1 | 0 / 5 | |
| 1.6.0 | 0 / 5 | |
| 1.5.0 | 0 / 5 | |
| 1.4.1 | 0 / 5 | |
| 1.4.0 | 0 / 5 | |
| 1.3.0 | 0 / 5 |
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.