devtools
A Chrome DevTools protocol binding that maps WebDriver commands into Chrome DevTools commands using Puppeteer
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:chrome-launcher | AI (phantom-deps): chrome-launcher used dynamically; phantom-dep pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/ua-parser-js | AI (phantom-deps): Framework-scoped type package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:query-selector-shadow-dom | AI (phantom-deps): query-selector-shadow-dom used dynamically; phantom-dep pattern is stable. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is used dynamically in devtools; phantom-dep pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:edge-paths | AI (phantom-deps): edge-paths is referenced in config; phantom-dep pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@wdio/types | AI (phantom-deps): @wdio/* packages loaded by convention in WebDriverIO ecosystem; stable. | ai | |
| phantom-deps | phantom-dep:@wdio/utils | AI (phantom-deps): @wdio/* packages loaded by convention in WebDriverIO ecosystem; stable. | ai | |
| phantom-deps | phantom-dep:@wdio/config | AI (phantom-deps): @wdio/* packages loaded by convention in WebDriverIO ecosystem; stable. | ai | |
| phantom-deps | phantom-dep:@wdio/logger | AI (phantom-deps): @wdio/* packages loaded by convention in WebDriverIO ecosystem; stable. | ai | |
| phantom-deps | phantom-dep:ua-parser-js | AI (phantom-deps): ua-parser-js used dynamically; phantom-dep pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:puppeteer-core | AI (phantom-deps): puppeteer-core used dynamically; phantom-dep pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:@wdio/protocols | AI (phantom-deps): @wdio/* packages loaded by convention in WebDriverIO ecosystem; stable. | ai |
Versions (showing 100 of 342)
| Version | Deps | Published |
|---|---|---|
| 8.11.3 | 14 / 2 | |
| 8.11.0 | 14 / 2 | |
| 8.10.7 | 14 / 2 | |
| 8.10.6 | 14 / 2 | |
| 8.10.5 | 14 / 2 | |
| 8.10.4 | 14 / 2 | |
| 8.10.2 | 14 / 2 | |
| 8.10.1 | 14 / 2 | |
| 8.10.0 | 14 / 2 | |
| 8.8.7 | 14 / 2 | |
| 8.8.6 | 14 / 2 | |
| 8.8.4 | 14 / 2 | |
| 8.8.2 | 14 / 2 | |
| 8.8.1 | 14 / 2 | |
| 8.8.0 | 14 / 2 | |
| 8.7.0 | 14 / 2 | |
| 8.6.9 | 14 / 2 | |
| 8.6.8 | 14 / 2 | |
| 8.6.6 | 14 / 2 | |
| 8.6.2 | 14 / 2 | |
| 8.6.1 | 14 / 2 | |
| 8.6.0 | 14 / 2 | |
| 8.5.9 | 14 / 2 | |
| 8.5.7 | 14 / 2 | |
| 8.5.6 | 14 / 2 | |
| 8.5.5 | 14 / 2 | |
| 8.5.1 | 14 / 2 | |
| 8.4.0 | 14 / 2 | |
| 8.3.11 | 14 / 2 | |
| 8.3.8 | 14 / 2 | |
| 8.3.5 | 14 / 2 | |
| 8.3.3 | 14 / 2 | |
| 8.3.2 | 14 / 2 | |
| 8.3.1 | 14 / 2 | |
| 8.3.0 | 14 / 2 | |
| 8.2.3 | 14 / 2 | |
| 8.2.2 | 14 / 2 | |
| 8.2.0 | 14 / 2 | |
| 8.1.3 | 14 / 2 | |
| 8.1.2 | 14 / 2 | |
| 8.1.0 | 14 / 2 | |
| 8.0.15 | 14 / 2 | |
| 8.0.14 | 14 / 2 | |
| 8.0.13 | 14 / 2 | |
| 8.0.11 | 14 / 2 | |
| 8.0.10 | 14 / 2 | |
| 8.0.9 | 14 / 2 | |
| 8.0.8 | 14 / 2 | |
| 8.0.7 | 14 / 2 | |
| 8.0.6 | 14 / 2 | |
| 8.0.2 | 14 / 2 | |
| 8.0.1 | 14 / 2 | |
| 8.0.0 | 14 / 2 | |
| 7.33.0 | 13 / 1 | |
| 7.32.0 | 13 / 1 | |
| 7.31.1 | 13 / 1 | |
| 7.31.0 | 13 / 1 | |
| 7.30.2 | 13 / 1 | |
| 7.30.0 | 13 / 1 | |
| 7.28.1 | 13 / 1 | |
| 7.28.0 | 13 / 1 | |
| 7.27.0 | 13 / 1 | |
| 7.26.0 | 13 / 1 | |
| 7.25.4 | 13 / 1 | |
| 7.25.1 | 13 / 1 | |
| 7.25.0 | 13 / 1 | |
| 7.24.1 | 13 / 1 | |
| 7.24.0 | 13 / 1 | |
| 7.23.0 | 13 / 1 | |
| 7.22.0 | 13 / 1 | |
| 7.21.0 | 13 / 1 | |
| 7.20.8 | 13 / 1 | |
| 7.20.7 | 13 / 1 | |
| 7.20.6 | 13 / 1 | |
| 7.20.4 | 13 / 1 | |
| 7.20.3 | 13 / 1 | |
| 7.20.2 | 13 / 1 | |
| 7.20.1 | 13 / 1 | |
| 7.20.0 | 13 / 1 | |
| 7.19.7 | 13 / 1 | |
| 7.19.5 | 13 / 1 | |
| 7.19.3 | 13 / 1 | |
| 7.19.2 | 13 / 1 | |
| 7.19.1 | 13 / 1 | |
| 7.19.0 | 13 / 1 | |
| 7.18.0 | 13 / 1 | |
| 7.17.3 | 13 / 1 | |
| 7.17.0 | 13 / 1 | |
| 7.16.16 | 13 / 1 | |
| 7.16.15 | 13 / 1 | |
| 7.16.14 | 13 / 1 | |
| 7.16.13 | 13 / 1 | |
| 7.16.12 | 13 / 1 | |
| 7.16.11 | 13 / 1 | |
| 7.16.10 | 13 / 1 | |
| 7.16.7 | 13 / 1 | |
| 7.16.5 | 13 / 1 | |
| 7.16.3 | 13 / 1 | |
| 7.16.2 | 12 / 2 | |
| 7.16.1 | 12 / 2 |
v8.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.