@nice-move/eslint-config-react
A `eslint` config for `react` project best practice
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate automation change for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint config packages reference plugins in config objects, not via import statements; phantom-dep is a stable false positive here. | ai | |
| dependencies | unvetted-dep:settingz | AI (dependencies): settingz is a companion package in the nice-move monorepo; consistent usage across versions of this config package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jsx-a11y | AI (phantom-deps): ESLint plugins are referenced in config objects, not imported directly; stable false positive. | ai | |
| phantom-deps | phantom-dep:globals | AI (phantom-deps): ESLint config packages reference plugins/globals in config objects, not via import statements; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): ESLint plugins are referenced in config objects, not imported directly; stable false positive. | ai | |
| phantom-deps | phantom-dep:settingz | AI (phantom-deps): Config-file reference pattern; not a real phantom dep for an ESLint config package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import-x | AI (phantom-deps): ESLint plugins are referenced in config objects, not imported directly; stable false positive. | ai |
Versions (showing 87 of 87)
| Version | Deps | Published |
|---|---|---|
| 0.15.7 | 11 / 0 | |
| 0.15.6 | 11 / 0 | |
| 0.15.5 | 11 / 0 | |
| 0.15.4 | 11 / 0 | |
| 0.15.3 | 11 / 0 | |
| 0.15.2 | 11 / 0 | |
| 0.15.1 | 11 / 0 | |
| 0.15.0 | 11 / 0 | |
| 0.14.3 | 11 / 0 | |
| 0.14.2 | 11 / 0 | |
| 0.14.0 | 11 / 0 | |
| 0.13.27 | 11 / 0 | |
| 0.13.26 | 11 / 0 | |
| 0.13.25 | 11 / 0 | |
| 0.13.24 | 11 / 0 | |
| 0.13.23 | 11 / 0 | |
| 0.13.22 | 11 / 0 | |
| 0.13.21 | 11 / 0 | |
| 0.13.20 | 11 / 0 | |
| 0.13.19 | 10 / 0 | |
| 0.13.17 | 10 / 0 | |
| 0.13.16 | 10 / 0 | |
| 0.13.15 | 10 / 0 | |
| 0.13.14 | 10 / 0 | |
| 0.13.13 | 10 / 0 | |
| 0.13.12 | 10 / 0 | |
| 0.13.11 | 10 / 0 | |
| 0.13.9 | 10 / 0 | |
| 0.13.8 | 10 / 0 | |
| 0.13.7 | 10 / 0 | |
| 0.13.6 | 10 / 0 | |
| 0.13.5 | 10 / 0 | |
| 0.13.4 | 10 / 0 | |
| 0.13.3 | 10 / 0 | |
| 0.13.2 | 10 / 0 | |
| 0.13.1 | 10 / 0 | |
| 0.13.0 | 10 / 0 | |
| 0.12.25 | 10 / 0 | |
| 0.12.24 | 10 / 0 | |
| 0.12.23 | 10 / 0 | |
| 0.12.22 | 10 / 0 | |
| 0.12.21 | 10 / 0 | |
| 0.12.20 | 10 / 0 | |
| 0.12.19 | 10 / 0 | |
| 0.12.18 | 10 / 0 | |
| 0.12.17 | 10 / 0 | |
| 0.12.16 | 10 / 0 | |
| 0.12.15 | 10 / 0 | |
| 0.12.14 | 10 / 0 | |
| 0.12.13 | 10 / 0 | |
| 0.12.12 | 10 / 0 | |
| 0.12.11 | 10 / 0 | |
| 0.12.10 | 10 / 0 | |
| 0.12.9 | 10 / 0 | |
| 0.12.8 | 10 / 0 | |
| 0.12.6 | 10 / 0 | |
| 0.12.5 | 10 / 0 | |
| 0.12.4 | 10 / 0 | |
| 0.12.3 | 10 / 0 | |
| 0.12.2 | 10 / 0 | |
| 0.12.1 | 10 / 0 | |
| 0.12.0 | 10 / 0 | |
| 0.11.34 | 6 / 0 | |
| 0.11.33 | 6 / 0 | |
| 0.11.32 | 6 / 0 | |
| 0.11.31 | 6 / 0 | |
| 0.11.30 | 6 / 0 | |
| 0.11.29 | 6 / 0 | |
| 0.11.28 | 6 / 0 | |
| 0.11.27 | 6 / 0 | |
| 0.11.26 | 6 / 0 | |
| 0.11.25 | 6 / 0 | |
| 0.11.24 | 6 / 0 | |
| 0.11.23 | 6 / 0 | |
| 0.11.22 | 6 / 0 | |
| 0.11.21 | 6 / 0 | |
| 0.11.20 | 6 / 0 | |
| 0.11.19 | 6 / 0 | |
| 0.11.18 | 6 / 0 | |
| 0.11.17 | 6 / 0 | |
| 0.11.13 | 6 / 0 | |
| 0.11.12 | 6 / 0 | |
| 0.11.11 | 6 / 0 | |
| 0.11.10 | 6 / 0 | |
| 0.11.9 | 6 / 0 | |
| 0.11.8 | 6 / 0 | |
| 0.11.7 | 6 / 0 |
v0.15.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.