extract-text-webpack-plugin
Extract text from bundle into a file.
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): Legitimate maintainer transition within webpack-contrib org; d3viant0ne is an established publisher with strong track record. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive: thelarkinn is a webpack core maintainer; no-keywords and small entry point are normal for this compiled webpack plugin. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 4 / 21 | |
| 3.0.1 | 4 / 21 | |
| 3.0.0 | 4 / 21 | |
| 2.1.2 | 4 / 12 | |
| 2.1.1 | 4 / 12 | |
| 2.1.0 | 4 / 12 | |
| 2.0.0 | 4 / 12 | |
| 1.0.1 | 3 / 11 | |
| 1.0.0 | 2 / 11 | |
| 0.9.1 | 2 / 11 | |
| 0.9.0 | 2 / 11 | |
| 0.8.2 | 2 / 4 | |
| 0.8.1 | 3 / 4 | |
| 0.8.0 | 3 / 4 | |
| 0.7.1 | 3 / 4 | |
| 0.7.0 | 3 / 4 | |
| 0.6.0 | 3 / 4 | |
| 0.5.0 | 3 / 4 | |
| 0.4.0 | 3 / 4 | |
| 0.3.8 | 3 / 4 | |
| 0.3.7 | 3 / 4 | |
| 0.3.6 | 3 / 4 | |
| 0.3.5 | 3 / 4 | |
| 0.3.4 | 3 / 4 | |
| 0.3.3 | 3 / 4 | |
| 0.3.2 | 3 / 4 | |
| 0.3.1 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.5 | 2 / 3 | |
| 0.2.4 | 2 / 3 | |
| 0.2.3 | 2 / 3 | |
| 0.2.2 | 2 / 3 | |
| 0.2.1 | 2 / 3 | |
| 0.2.0 | 2 / 3 | |
| 0.1.2 | 2 / 1 | |
| 0.1.1 | 2 / 1 | |
| 0.1.0 | 0 / 0 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2017-07-10. 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.
v2.1.2
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 2017-06-08. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
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 2017-03-05. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
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 2017-02-24. This could indicate a legitimate maintainer transition or an account compromise.