@wdio/config
A helper utility to parse and validate WebdriverIO options
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:jiti | AI (dependencies): jiti is a well-known TypeScript/ESM runtime loader used across the JS ecosystem; its use in wdio-config for loading TS config files is expected and legitimate. | ai | |
| phantom-deps | phantom-dep:@wdio/utils | AI (phantom-deps): Same-org monorepo dependency; indirect imports are normal in the WebdriverIO monorepo structure. | ai | |
| phantom-deps | phantom-dep:import-meta-resolve | AI (phantom-deps): Used indirectly via config file resolution logic; not a security concern for this package. | ai |
Versions (showing 100 of 297)
| Version | Deps | Published |
|---|---|---|
| 8.16.12 | 8 / 2 | |
| 8.16.11 | 8 / 2 | |
| 8.16.10 | 8 / 2 | |
| 8.16.9 | 8 / 2 | |
| 8.16.7 | 8 / 2 | |
| 8.16.3 | 8 / 2 | |
| 8.16.0 | 8 / 2 | |
| 8.15.10 | 8 / 2 | |
| 8.15.9 | 8 / 2 | |
| 8.15.8 | 8 / 2 | |
| 8.15.7 | 8 / 2 | |
| 8.15.6 | 8 / 2 | |
| 8.15.4 | 8 / 2 | |
| 8.15.0 | 8 / 2 | |
| 8.14.6 | 8 / 2 | |
| 8.14.0 | 8 / 2 | |
| 8.13.13 | 8 / 2 | |
| 8.12.1 | 8 / 2 | |
| 8.11.3 | 8 / 2 | |
| 8.11.0 | 8 / 2 | |
| 8.10.7 | 8 / 2 | |
| 8.10.6 | 8 / 2 | |
| 8.10.4 | 8 / 2 | |
| 8.10.2 | 8 / 2 | |
| 8.10.1 | 8 / 2 | |
| 8.10.0 | 8 / 2 | |
| 8.8.7 | 8 / 2 | |
| 8.8.6 | 8 / 2 | |
| 8.8.4 | 8 / 2 | |
| 8.8.0 | 8 / 2 | |
| 8.7.0 | 8 / 2 | |
| 8.6.8 | 8 / 2 | |
| 8.6.6 | 8 / 2 | |
| 8.6.2 | 8 / 2 | |
| 8.6.1 | 8 / 2 | |
| 8.6.0 | 8 / 2 | |
| 8.5.6 | 8 / 2 | |
| 8.5.5 | 8 / 2 | |
| 8.5.1 | 8 / 2 | |
| 8.4.0 | 8 / 2 | |
| 8.3.11 | 8 / 2 | |
| 8.3.2 | 8 / 2 | |
| 8.3.1 | 8 / 2 | |
| 8.3.0 | 8 / 2 | |
| 8.2.3 | 8 / 2 | |
| 8.2.2 | 8 / 2 | |
| 8.2.0 | 8 / 2 | |
| 8.1.2 | 8 / 2 | |
| 8.1.0 | 8 / 2 | |
| 8.0.14 | 8 / 2 | |
| 8.0.13 | 8 / 2 | |
| 8.0.11 | 8 / 2 | |
| 8.0.10 | 8 / 2 | |
| 8.0.9 | 8 / 2 | |
| 8.0.8 | 8 / 2 | |
| 8.0.7 | 8 / 2 | |
| 8.0.6 | 8 / 2 | |
| 8.0.2 | 8 / 2 | |
| 8.0.0 | 8 / 2 | |
| 7.33.0 | 6 / 2 | |
| 7.31.1 | 6 / 2 | |
| 7.31.0 | 6 / 2 | |
| 7.30.2 | 5 / 2 | |
| 7.30.0 | 5 / 2 | |
| 7.26.0 | 5 / 2 | |
| 7.25.4 | 5 / 2 | |
| 7.25.1 | 5 / 2 | |
| 7.25.0 | 5 / 2 | |
| 7.24.1 | 5 / 2 | |
| 7.24.0 | 5 / 2 | |
| 7.23.0 | 5 / 2 | |
| 7.21.0 | 5 / 2 | |
| 7.20.8 | 5 / 2 | |
| 7.20.7 | 5 / 2 | |
| 7.20.6 | 5 / 2 | |
| 7.20.3 | 5 / 2 | |
| 7.20.1 | 5 / 2 | |
| 7.20.0 | 5 / 2 | |
| 7.19.5 | 4 / 2 | |
| 7.19.1 | 4 / 2 | |
| 7.19.0 | 4 / 2 | |
| 7.18.0 | 4 / 2 | |
| 7.17.3 | 4 / 2 | |
| 7.16.16 | 4 / 2 | |
| 7.16.14 | 4 / 2 | |
| 7.16.13 | 4 / 2 | |
| 7.16.11 | 4 / 2 | |
| 7.16.3 | 4 / 2 | |
| 7.16.1 | 4 / 2 | |
| 7.16.0 | 4 / 2 | |
| 7.14.1 | 4 / 2 | |
| 7.13.2 | 4 / 2 | |
| 7.13.0 | 4 / 2 | |
| 7.12.5 | 4 / 2 | |
| 7.10.1 | 4 / 2 | |
| 7.8.0 | 4 / 2 | |
| 7.7.7 | 4 / 2 | |
| 7.7.5 | 4 / 2 | |
| 7.7.3 | 4 / 2 | |
| 7.7.0 | 4 / 2 |
v8.16.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.13.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.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.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.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.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.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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.