webpack-manifest-plugin
A Webpack Plugin for generating Asset Manifests
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:mutexify | AI (dependencies): mutexify is a well-known, benign mutex utility; its use in a file-writing webpack plugin is appropriate and poses no meaningful risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): fs-extra is a widely-used, legitimate Node.js filesystem utility package; its addition is consistent with the plugin's manifest file-writing functionality. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from danethurber to mastilver occurred in 2017; mastilver is a known ecosystem contributor and legitimate maintainer of this package. Stable historical transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mastilver is a well-known contributor to webpack-manifest-plugin; this is a legitimate maintainer addition from 2017, not a suspicious takeover. | ai | |
| provenance | missing-githead | AI (provenance): shellscape is an established publisher with strong track record; missing gitHead reflects a publish environment change, not a security concern for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by a major version bump with modernized tooling (vitest, updated node engine) is consistent with legitimate maintenance by a trusted publisher with a clean track record. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a trusted publisher with a clean track record; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:tapable | AI (dependencies): tapable is a core webpack ecosystem package maintained by the webpack team; it is a standard and expected dependency for any webpack plugin. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 2 / 24 | |
| 6.0.0 | 2 / 24 | |
| 5.0.1 | 2 / 28 | |
| 5.0.0 | 2 / 28 | |
| 4.1.1 | 2 / 30 | |
| 4.1.0 | 2 / 30 | |
| 4.0.2 | 2 / 30 | |
| 4.0.1 | 2 / 30 | |
| 4.0.0 | 2 / 30 | |
| 3.2.0 | 2 / 21 | |
| 3.1.1 | 2 / 20 | |
| 3.1.0 | 2 / 20 | |
| 3.0.0 | 2 / 20 | |
| 2.2.0 | 4 / 11 | |
| 2.1.2 | 4 / 11 | |
| 2.1.1 | 4 / 11 | |
| 2.1.0 | 3 / 11 | |
| 2.0.4 | 3 / 11 | |
| 2.0.3 | 3 / 11 | |
| 2.0.2 | 3 / 9 | |
| 2.0.1 | 3 / 9 | |
| 2.0.0 | 3 / 9 | |
| 1.3.2 | 2 / 10 | |
| 1.3.1 | 2 / 10 | |
| 1.3.0 | 3 / 10 | |
| 1.2.1 | 2 / 10 | |
| 1.2.0 | 2 / 10 | |
| 1.1.2 | 2 / 6 | |
| 1.1.1 | 2 / 6 | |
| 1.1.0 | 2 / 6 | |
| 1.0.1 | 1 / 6 | |
| 1.0.0 | 1 / 6 | |
| 0.5.0 | 1 / 6 | |
| 0.4.0 | 1 / 6 | |
| 0.3.0 | 1 / 6 | |
| 0.2.0 | 1 / 6 | |
| 0.0.2 | 1 / 6 | |
| 0.0.1 | 1 / 6 |
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
2 findingsThis version was published by a different npm account than previous versions on 2021-04-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-03-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package 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 2020-12-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2019-09-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2019-09-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsThis version was published by a different npm account than previous versions on 2018-09-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsThis version was published by a different npm account than previous versions on 2018-05-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2018-04-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2018-04-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-04-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
2 findingsThis version was published by a different npm account than previous versions on 2017-09-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsThis version was published by a different npm account than previous versions on 2017-08-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2017-08-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsThis version was published by a different npm account than previous versions on 2017-07-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2017-07-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsThis version was published by a different npm account than previous versions on 2017-07-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2017-07-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.