@serenity-js/webdriverio
Adapter that integrates @serenity-js/web with the latest stable version of WebdriverIO, enabling Serenity/JS reporting and using the Screenplay Pattern to write web and mobile test scenarios
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used for WebdriverIO browser script serialization/rehydration — established pattern in this package, not untrusted input. | ai | |
| dependencies | unvetted-dep:@serenity-js/core | AI (dependencies): First-party sibling package from the serenity-js monorepo. | ai | |
| dependencies | unvetted-dep:@serenity-js/web | AI (dependencies): First-party sibling package from the serenity-js monorepo. | ai | |
| dependencies | unvetted-dep:@serenity-js/rest | AI (dependencies): First-party sibling package from the serenity-js monorepo. | ai | |
| dependencies | unvetted-dep:@wdio/reporter | AI (dependencies): Official WebdriverIO reporter package, well-known ecosystem dependency. | ai | |
| dependencies | unvetted-dep:tiny-types | AI (dependencies): Long-standing dependency of serenity-js packages; stable utility library. | ai |
Versions (showing 23 of 123)
| Version | Deps | Published |
|---|---|---|
| 3.8.0 | 5 / 17 | |
| 3.7.2 | 5 / 17 | |
| 3.7.1 | 5 / 17 | |
| 3.7.0 | 5 / 17 | |
| 3.6.1 | 5 / 17 | |
| 3.6.0 | 5 / 17 | |
| 3.5.0 | 5 / 17 | |
| 3.4.2 | 5 / 17 | |
| 3.4.1 | 5 / 17 | |
| 3.4.0 | 5 / 17 | |
| 3.3.1 | 5 / 17 | |
| 3.3.0 | 5 / 17 | |
| 3.2.1 | 5 / 17 | |
| 3.2.0 | 5 / 17 | |
| 3.1.6 | 6 / 16 | |
| 3.1.5 | 6 / 17 | |
| 3.1.4 | 6 / 17 | |
| 3.1.3 | 6 / 17 | |
| 3.1.2 | 6 / 17 | |
| 3.1.1 | 6 / 17 | |
| 3.1.0 | 6 / 17 | |
| 3.0.1 | 6 / 17 | |
| 3.0.0 | 6 / 17 |
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.