@abinnovision/eslint-config-react
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI publisher is a standard org automation pattern for this package family. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): ESLint config pattern; plugins referenced in extends, not imported. | ai | |
| phantom-deps | phantom-dep:@eslint-react/eslint-plugin | AI (phantom-deps): ESLint config pattern; plugins referenced in extends, not imported. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-better-tailwindcss | AI (phantom-deps): ESLint config pattern; plugins referenced in extends, not imported. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 3 / 7 | |
| 3.1.1 | 3 / 7 | |
| 3.1.0 | 3 / 6 | |
| 3.0.3 | 3 / 6 | |
| 3.0.2 | 3 / 6 | |
| 3.0.1 | 3 / 6 | |
| 3.0.0 | 3 / 6 |
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
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.