webpack-log
A logger for the Webpack ecosystem
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 michael-ciniawsky to shellscape (webpack ecosystem collaborator) in 2019; shellscape owns the GitHub repo. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of bebraw is consistent with the project transfer to shellscape; both are known webpack ecosystem contributors. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 3 / 10 | |
| 3.0.1 | 3 / 12 | |
| 3.0.0 | 3 / 12 | |
| 2.0.0 | 2 / 9 | |
| 1.2.0 | 4 / 9 | |
| 1.1.2 | 4 / 9 | |
| 1.1.1 | 4 / 9 | |
| 1.1.0 | 4 / 9 | |
| 1.0.2 | 3 / 9 | |
| 1.0.1 | 3 / 9 | |
| 1.0.0 | 3 / 9 |
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 2019-08-01. 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.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 2018-08-23. This could indicate a legitimate maintainer transition or an account compromise.