eslint-loader
A ESlint loader for webpack
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): webpack-contrib org maintainer rotation; ricardogobbosouza is a known webpack-contrib contributor. Transition is consistent with org practices and no code changes were introduced. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 5 / 26 | |
| 4.0.1 | 5 / 26 | |
| 4.0.0 | 5 / 27 | |
| 3.0.4 | 5 / 27 | |
| 3.0.3 | 5 / 27 | |
| 3.0.2 | 5 / 27 | |
| 3.0.1 | 4 / 28 | |
| 3.0.0 | 4 / 28 | |
| 2.2.1 | 5 / 10 | |
| 2.2.0 | 5 / 10 | |
| 2.1.2 | 5 / 10 | |
| 2.1.1 | 5 / 10 | |
| 2.1.0 | 5 / 10 | |
| 2.0.0 | 5 / 5 | |
| 1.9.0 | 5 / 5 | |
| 1.8.0 | 5 / 5 | |
| 1.7.1 | 6 / 5 | |
| 1.7.0 | 6 / 5 | |
| 1.6.3 | 4 / 5 | |
| 1.6.2 | 4 / 5 | |
| 1.6.1 | 4 / 5 | |
| 1.6.0 | 3 / 5 | |
| 1.5.0 | 3 / 5 | |
| 1.4.1 | 2 / 5 | |
| 1.4.0 | 2 / 5 | |
| 1.3.0 | 2 / 5 | |
| 1.2.1 | 2 / 5 | |
| 1.2.0 | 2 / 4 | |
| 1.1.1 | 2 / 4 | |
| 1.1.0 | 2 / 4 | |
| 1.0.0 | 2 / 4 | |
| 0.14.2 | 2 / 4 | |
| 0.14.1 | 2 / 4 | |
| 0.14.0 | 2 / 4 | |
| 0.13.0 | 2 / 4 | |
| 0.12.0 | 2 / 4 | |
| 0.11.2 | 2 / 4 | |
| 0.11.1 | 2 / 4 | |
| 0.11.0 | 2 / 4 | |
| 0.10.0 | 2 / 4 | |
| 0.9.0 | 2 / 4 | |
| 0.8.0 | 2 / 4 | |
| 0.7.0 | 1 / 4 | |
| 0.6.0 | 1 / 4 | |
| 0.5.0 | 1 / 3 | |
| 0.4.0 | 4 / 4 | |
| 0.3.0 | 4 / 4 | |
| 0.2.1 | 4 / 4 | |
| 0.2.0 | 4 / 4 | |
| 0.1.0 | 4 / 4 |
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2019-09-25. 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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.