@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, so a manually published version cannot be tied back to a reviewed commit.
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 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 5.5.53 | 4 / 5 | |
| 5.5.52 | 4 / 5 | |
| 5.5.51 | 4 / 5 | |
| 5.5.50 | 4 / 5 | |
| 5.5.49 | 4 / 5 | |
| 5.5.48 | 4 / 5 | |
| 5.5.47 | 4 / 5 |
v5.5.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.