@wordpress/e2e-tests
Test plugins and mu-plugins for E2E tests in WordPress.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Test/config-referenced dep in a test suite package; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Test/config-referenced dep in a test suite package; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:@wordpress/url | AI (phantom-deps): Same-org WordPress dep used in test configs; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:expect-puppeteer | AI (phantom-deps): Test/config-referenced dep in a test suite package; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:@wordpress/jest-console | AI (phantom-deps): Same-org WordPress dep used in test configs; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@wordpress/jest-puppeteer-axe | AI (phantom-deps): Same-org WordPress dep used in test configs; stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 9.13.0 | 2 / 0 | |
| 9.12.0 | 2 / 0 | |
| 9.11.0 | 2 / 0 | |
| 9.10.0 | 2 / 0 | |
| 9.9.0 | 2 / 0 | |
| 9.8.0 | 2 / 0 | |
| 9.7.0 | 2 / 0 | |
| 9.6.0 | 2 / 0 | |
| 9.5.0 | 2 / 0 | |
| 9.4.0 | 2 / 0 | |
| 9.3.0 | 2 / 0 | |
| 9.2.0 | 2 / 0 | |
| 9.1.0 | 2 / 0 | |
| 9.0.0 | 2 / 0 | |
| 8.33.4 | 13 / 0 | |
| 8.33.3 | 13 / 0 | |
| 8.33.2 | 13 / 0 |
v9.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.33.4
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 (peterwilsoncc) than the most recent previously approved version (gutenbergplugin) on 2026-01-29, but peterwilsoncc 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.
v8.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.