@wordpress/e2e-test-utils
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
Keywords
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 11.34.0 | 6 / 0 | |
| 11.33.1 | 6 / 0 | |
| 11.33.0 | 6 / 0 | |
| 11.32.0 | 7 / 0 | |
| 11.31.0 | 7 / 0 | |
| 11.30.0 | 7 / 0 | |
| 11.29.0 | 7 / 0 | |
| 11.28.0 | 7 / 0 | |
| 11.27.0 | 7 / 0 | |
| 11.26.0 | 7 / 0 | |
| 11.25.0 | 7 / 0 | |
| 11.24.0 | 7 / 0 | |
| 11.23.0 | 7 / 0 | |
| 11.22.0 | 7 / 0 | |
| 11.21.0 | 7 / 0 | |
| 11.20.0 | 7 / 0 | |
| 11.19.2 | 7 / 0 | |
| 11.19.1 | 7 / 0 | |
| 11.19.0 | 7 / 0 | |
| 11.18.0 | 7 / 0 | |
| 11.17.0 | 7 / 0 | |
| 11.16.0 | 7 / 0 | |
| 11.15.1 | 7 / 0 | |
| 11.15.0 | 7 / 0 | |
| 11.14.0 | 7 / 0 | |
| 11.13.0 | 7 / 0 | |
| 11.12.0 | 7 / 0 | |
| 11.11.0 | 7 / 0 | |
| 11.10.0 | 7 / 0 | |
| 11.9.0 | 7 / 0 | |
| 11.8.2 | 7 / 0 | |
| 11.8.1 | 7 / 0 | |
| 11.8.0 | 7 / 0 | |
| 11.7.0 | 7 / 0 | |
| 11.6.0 | 7 / 0 | |
| 11.5.0 | 7 / 0 | |
| 11.4.0 | 7 / 0 | |
| 11.3.0 | 7 / 0 | |
| 11.2.0 | 7 / 0 | |
| 11.1.0 | 7 / 0 | |
| 11.0.1 | 7 / 0 | |
| 11.0.0 | 7 / 0 |
v11.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gutenbergplugin) than the most recent previously approved version (gziolo) on 2025-05-07, but gutenbergplugin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.22.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-04-11, but gziolo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gutenbergplugin) than the most recent previously approved version (gziolo) on 2025-01-15, but gutenbergplugin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.15.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gutenbergplugin) than the most recent previously approved version (gziolo) on 2025-01-03, but gutenbergplugin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.15.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-01-03, but gziolo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v11.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.