eslint-config-standard
JavaScript Standard Style - 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): Legitimate maintainer transition from linusu to voxpelli within the standard org; voxpelli is a well-established publisher. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known maintainer additions (jhiesey, voxpelli) as part of the standard project's governance evolution. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 17.1.0 | 0 / 7 | |
| 17.0.0 | 0 / 7 | |
| 16.0.3 | 0 / 5 | |
| 16.0.2 | 0 / 5 | |
| 16.0.1 | 0 / 5 | |
| 16.0.0 | 0 / 5 | |
| 15.0.1 | 0 / 6 | |
| 15.0.0 | 0 / 6 | |
| 14.1.1 | 0 / 6 | |
| 14.1.0 | 0 / 6 | |
| 14.0.1 | 0 / 6 | |
| 14.0.0 | 0 / 6 | |
| 13.0.1 | 0 / 6 | |
| 13.0.0 | 0 / 6 | |
| 12.0.0 | 0 / 6 | |
| 11.0.0 | 0 / 6 | |
| 10.2.1 | 0 / 6 | |
| 10.2.0 | 0 / 6 | |
| 10.1.0 | 0 / 6 | |
| 10.0.0 | 0 / 6 | |
| 8.0.0 | 0 / 6 | |
| 7.1.0 | 0 / 4 | |
| 7.0.3 | 0 / 4 | |
| 7.0.2 | 0 / 4 | |
| 7.0.1 | 0 / 4 | |
| 7.0.0 | 0 / 4 | |
| 6.2.1 | 0 / 4 | |
| 6.2.0 | 0 / 4 | |
| 6.1.0 | 0 / 4 | |
| 6.0.1 | 0 / 4 | |
| 6.0.0 | 0 / 4 | |
| 5.3.5 | 0 / 4 | |
| 5.3.4 | 0 / 4 | |
| 5.3.3 | 0 / 4 | |
| 5.3.2 | 0 / 4 | |
| 5.3.1 | 0 / 4 | |
| 5.3.0 | 0 / 4 | |
| 5.2.0 | 0 / 4 | |
| 5.1.0 | 0 / 4 | |
| 5.0.0 | 0 / 3 | |
| 4.4.0 | 0 / 3 | |
| 4.3.2 | 0 / 3 | |
| 4.3.1 | 0 / 3 | |
| 4.3.0 | 0 / 3 | |
| 4.2.0 | 0 / 3 | |
| 4.1.0 | 0 / 3 | |
| 4.0.0 | 0 / 3 | |
| 3.4.1 | 0 / 1 | |
| 3.4.0 | 0 / 1 | |
| 3.3.0 | 0 / 1 | |
| 3.2.0 | 0 / 1 |
v17.0.0
2 findingsThis version was published by a different npm account than previous versions on 2022-04-20. 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.
v16.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-05-24. This could indicate a legitimate maintainer transition or an account compromise.
v16.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.