@wdio/lighthouse-service
A WebdriverIO service that allows you to run Chrome DevTools commands in your tests
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): webdriverio monorepo migrated to GitHub Actions CI publishing with SLSA attestation; expected for this org. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Build tooling convention in wdio monorepo; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only declaration; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:istanbul-lib-report | AI (phantom-deps): Referenced in coverage config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-istanbul | AI (phantom-deps): Referenced in coverage config; stable false positive for this package. | ai |
Versions (showing 98 of 98)
| Version | Deps | Published |
|---|---|---|
| 9.30.0 | 13 / 5 | |
| 9.29.1 | 13 / 5 | |
| 9.29.0 | 13 / 5 | |
| 9.28.0 | 13 / 5 | |
| 9.27.2 | 13 / 5 | |
| 9.27.1 | 13 / 5 | |
| 9.27.0 | 13 / 5 | |
| 9.26.1 | 13 / 5 | |
| 9.26.0 | 13 / 5 | |
| 9.25.0 | 13 / 5 | |
| 9.24.0 | 13 / 5 | |
| 9.23.3 | 13 / 5 | |
| 9.23.2 | 13 / 5 | |
| 9.23.1 | 13 / 5 | |
| 9.23.0 | 13 / 5 | |
| 9.22.0 | 13 / 5 | |
| 9.21.0 | 13 / 5 | |
| 9.20.1 | 13 / 5 | |
| 9.20.0 | 13 / 5 | |
| 9.19.2 | 13 / 5 | |
| 9.19.1 | 13 / 5 | |
| 9.19.0 | 13 / 5 | |
| 9.18.4 | 13 / 5 | |
| 9.18.3 | 13 / 5 | |
| 9.18.1 | 13 / 5 | |
| 9.18.0 | 13 / 5 | |
| 9.17.0 | 13 / 5 | |
| 9.16.2 | 13 / 5 | |
| 9.16.1 | 13 / 5 | |
| 9.16.0 | 13 / 5 | |
| 9.15.0 | 13 / 5 | |
| 9.14.0 | 13 / 5 | |
| 9.13.0 | 13 / 5 | |
| 9.12.7 | 13 / 5 | |
| 9.12.6 | 13 / 5 | |
| 9.12.5 | 13 / 5 | |
| 9.12.4 | 13 / 5 | |
| 9.12.3 | 13 / 5 | |
| 9.12.2 | 13 / 5 | |
| 9.12.1 | 13 / 5 | |
| 9.12.0 | 13 / 5 | |
| 9.11.0 | 13 / 5 | |
| 9.10.1 | 13 / 5 | |
| 9.10.0 | 13 / 5 | |
| 9.9.3 | 13 / 5 | |
| 9.9.2 | 13 / 5 | |
| 9.9.1 | 13 / 5 | |
| 9.9.0 | 13 / 5 | |
| 9.8.0 | 13 / 5 | |
| 9.7.3 | 13 / 5 | |
| 9.7.2 | 13 / 5 | |
| 9.7.1 | 13 / 5 | |
| 9.7.0 | 13 / 5 | |
| 9.6.4 | 13 / 5 | |
| 9.6.3 | 13 / 5 | |
| 9.6.2 | 13 / 5 | |
| 9.6.1 | 13 / 5 | |
| 9.6.0 | 13 / 5 | |
| 9.5.7 | 13 / 5 | |
| 9.5.6 | 13 / 5 | |
| 9.5.4 | 13 / 5 | |
| 9.5.3 | 13 / 5 | |
| 9.5.2 | 13 / 5 | |
| 9.5.1 | 13 / 5 | |
| 9.5.0 | 13 / 5 | |
| 9.4.5 | 13 / 5 | |
| 9.4.4 | 13 / 5 | |
| 9.4.3 | 13 / 5 | |
| 9.4.2 | 13 / 5 | |
| 9.4.1 | 13 / 5 | |
| 9.4.0 | 13 / 5 | |
| 9.3.1 | 13 / 5 | |
| 9.3.0 | 13 / 5 | |
| 9.2.14 | 13 / 5 | |
| 9.2.12 | 13 / 5 | |
| 9.2.11 | 13 / 5 | |
| 9.2.10 | 13 / 5 | |
| 9.2.8 | 13 / 5 | |
| 9.2.6 | 13 / 5 | |
| 9.2.5 | 13 / 5 | |
| 9.2.4 | 13 / 5 | |
| 9.2.2 | 13 / 5 | |
| 9.2.1 | 13 / 5 | |
| 9.2.0 | 13 / 5 | |
| 9.1.5 | 13 / 5 | |
| 9.1.4 | 13 / 5 | |
| 9.1.3 | 13 / 5 | |
| 9.1.2 | 13 / 5 | |
| 9.1.1 | 13 / 5 | |
| 9.1.0 | 13 / 5 | |
| 9.0.9 | 13 / 5 | |
| 9.0.8 | 13 / 5 | |
| 9.0.7 | 13 / 5 | |
| 9.0.6 | 13 / 5 | |
| 9.0.5 | 13 / 5 | |
| 9.0.4 | 13 / 5 | |
| 9.0.1 | 13 / 5 | |
| 9.0.0 | 13 / 5 |
v9.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.12.1
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.1
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
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.1
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.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
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.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
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.