@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 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.13
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.