eslint-config-standard-react
JavaScript Standard Style React/JSX support - ESLint Shareable Config
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from feross to voxpelli is a documented, legitimate maintainer handoff within the standard org. voxpelli has 823 approved packages and no rejections. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are known contributors to the standard ecosystem; this reflects a legitimate org-level transition, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is explained by the maintainer transition period. Publisher voxpelli is well-established with a clean track record. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 13.0.0 | 0 / 3 | |
| 12.0.0 | 0 / 3 | |
| 11.0.1 | 0 / 3 | |
| 11.0.0 | 0 / 3 | |
| 10.0.0 | 1 / 3 | |
| 9.2.0 | 1 / 3 | |
| 9.1.0 | 1 / 3 | |
| 9.0.0 | 1 / 3 | |
| 8.0.0 | 1 / 3 | |
| 7.0.2 | 1 / 3 | |
| 7.0.1 | 1 / 3 | |
| 7.0.0 | 1 / 3 | |
| 6.0.0 | 1 / 3 | |
| 5.0.0 | 1 / 3 | |
| 4.3.0 | 1 / 3 | |
| 4.2.0 | 1 / 3 | |
| 4.1.0 | 1 / 3 | |
| 4.0.2 | 1 / 3 | |
| 4.0.1 | 1 / 3 | |
| 4.0.0 | 1 / 3 | |
| 3.0.0 | 1 / 3 | |
| 2.5.1 | 1 / 3 | |
| 2.5.0 | 1 / 3 | |
| 2.4.0 | 1 / 3 | |
| 2.3.0 | 1 / 3 | |
| 2.2.0 | 1 / 3 | |
| 2.1.0 | 1 / 1 | |
| 2.0.0 | 0 / 1 | |
| 1.2.1 | 0 / 1 | |
| 1.2.0 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.5 | 0 / 1 | |
| 1.0.4 | 0 / 1 | |
| 1.0.3 | 0 / 1 | |
| 1.0.2 | 0 / 1 | |
| 1.0.1 | 0 / 1 | |
| 1.0.0 | 0 / 1 |
v12.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-10-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.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.