@rushstack/webpack5-module-minifier-plugin
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/estree | AI (phantom-deps): Type-only package used as a framework-scoped type dependency; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@types/tapable | AI (phantom-deps): Type-only package used as a framework-scoped type dependency; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@rushstack/worker-pool | AI (phantom-deps): Same org scope (@rushstack); likely loaded indirectly via worker pool internals rather than direct import. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 5.8.18 | 4 / 7 | |
| 5.8.15 | 4 / 7 | |
| 5.8.14 | 4 / 7 | |
| 5.8.13 | 4 / 7 | |
| 5.8.12 | 4 / 7 | |
| 5.8.8 | 4 / 7 | |
| 5.8.7 | 4 / 7 | |
| 5.8.5 | 4 / 7 | |
| 5.8.4 | 4 / 7 | |
| 5.8.2 | 4 / 7 | |
| 5.8.0 | 4 / 7 | |
| 5.6.14 | 4 / 7 | |
| 5.6.12 | 4 / 7 | |
| 5.6.7 | 4 / 7 | |
| 5.6.5 | 4 / 7 | |
| 5.6.4 | 4 / 7 | |
| 5.6.3 | 4 / 7 | |
| 5.6.2 | 4 / 7 | |
| 5.6.1 | 4 / 7 | |
| 5.6.0 | 4 / 7 | |
| 5.5.114 | 4 / 7 | |
| 5.5.113 | 4 / 7 | |
| 5.5.112 | 4 / 7 | |
| 5.5.111 | 4 / 7 | |
| 5.5.110 | 4 / 7 | |
| 5.5.109 | 4 / 7 | |
| 5.5.108 | 4 / 7 | |
| 5.5.107 | 4 / 6 | |
| 5.5.106 | 4 / 6 |
v5.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.