@hizzlewp/dependency-extraction-webpack-plugin
Custom Webpack plugin to map @hizzlewp imports to window.hizzlewp
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@wordpress/dependency-extraction-webpack-plugin | AI (dependencies): Official WordPress core tooling package; stable and widely trusted upstream dependency. | ai | |
| license | copyleft-license:GPL-2.0-or-later | AI (license): GPL-2.0-or-later is the declared and expected license for this WordPress-ecosystem package; stable across versions. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.6.13 | 1 / 0 | |
| 1.6.12 | 1 / 0 | |
| 1.6.11 | 1 / 0 | |
| 1.6.10 | 1 / 0 | |
| 1.6.9 | 1 / 0 | |
| 1.6.8 | 1 / 0 | |
| 1.6.7 | 1 / 0 | |
| 1.6.6 | 1 / 0 | |
| 1.6.3 | 1 / 0 | |
| 1.6.2 | 1 / 0 | |
| 1.6.1 | 1 / 0 | |
| 1.6.0 | 1 / 0 | |
| 1.5.0 | 1 / 0 | |
| 1.4.2 | 1 / 0 | |
| 1.4.1 | 1 / 0 | |
| 1.4.0 | 1 / 0 | |
| 1.3.14 | 1 / 0 | |
| 1.3.13 | 1 / 0 | |
| 1.3.12 | 1 / 0 | |
| 1.3.11 | 1 / 0 | |
| 1.3.10 | 1 / 0 | |
| 1.3.9 | 1 / 0 | |
| 1.3.8 | 1 / 0 | |
| 1.3.7 | 1 / 0 | |
| 1.3.6 | 1 / 0 | |
| 1.3.5 | 1 / 0 | |
| 1.3.4 | 1 / 0 | |
| 1.3.3 | 1 / 0 | |
| 1.3.2 | 1 / 0 | |
| 1.3.1 | 1 / 0 | |
| 1.3.0 | 1 / 1 | |
| 1.2.1 | 1 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.0 | 1 / 1 |
v1.6.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.