webpack-chain
[![NPM version][npm-image]][npm-url] [![NPM downloads][npm-downloads]][npm-url] [![Build Status][travis-image]][travis-url]
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): edmorley is a known neutrinojs org member; legitimate maintainer transition within the same project. | ai | |
| provenance | missing-githead | AI (provenance): Publish environment changed with maintainer transition; no code changes to be concerned about. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is core webpack-chain functionality for resolving plugin paths; intentional and documented in code. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2019, before npm provenance/Sigstore existed. Expected for this era of packages. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 6.5.1 | 2 / 13 | |
| 6.5.0 | 2 / 17 | |
| 6.4.0 | 2 / 17 | |
| 6.3.1 | 2 / 17 | |
| 6.3.0 | 2 / 17 | |
| 6.2.0 | 2 / 17 | |
| 6.1.0 | 2 / 17 | |
| 6.0.0 | 2 / 15 | |
| 5.2.4 | 2 / 13 | |
| 5.2.3 | 2 / 13 | |
| 5.2.2 | 2 / 13 | |
| 5.2.1 | 2 / 13 | |
| 5.2.0 | 2 / 13 | |
| 5.1.0 | 2 / 10 | |
| 5.0.1 | 2 / 10 | |
| 5.0.0 | 2 / 10 | |
| 4.12.1 | 2 / 10 | |
| 4.12.0 | 2 / 10 | |
| 4.11.0 | 2 / 10 | |
| 4.10.0 | 2 / 10 | |
| 4.9.0 | 2 / 10 | |
| 4.8.0 | 2 / 10 | |
| 4.7.0 | 2 / 10 | |
| 4.6.0 | 1 / 3 | |
| 4.5.0 | 1 / 3 | |
| 4.4.2 | 1 / 3 | |
| 4.4.1 | 1 / 3 | |
| 4.4.0 | 1 / 3 | |
| 4.3.0 | 1 / 3 | |
| 4.2.0 | 1 / 3 | |
| 4.1.0 | 1 / 3 | |
| 4.0.0 | 1 / 3 | |
| 3.3.0 | 1 / 2 | |
| 3.2.0 | 1 / 2 | |
| 3.1.0 | 1 / 2 | |
| 3.0.0 | 1 / 2 | |
| 2.0.1 | 1 / 2 | |
| 2.0.0 | 1 / 2 | |
| 1.4.3 | 1 / 0 | |
| 1.4.2 | 1 / 0 | |
| 1.4.1 | 1 / 0 | |
| 1.4.0 | 0 / 0 | |
| 1.3.0 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.3 | 0 / 0 | |
| 1.0.2 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.
v6.3.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.
v6.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.
v6.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.
v6.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.
This version was published by a different npm account than previous versions on 2019-12-13. 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.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
2 findings[Accepted risk] Package 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 2019-03-07. This could indicate a legitimate maintainer transition or an account compromise.
v5.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.
v5.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.
v5.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.
v5.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: edmorley.