@serenity-js/playwright
Adapter that integrates @serenity-js/web with Playwright, enabling Serenity/JS reporting and using the Screenplay Pattern to write component and end-to-end 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:tiny-types | AI (dependencies): tiny-types is a long-standing serenity-js ecosystem dependency, stable across many versions. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used for browser script serialization in Playwright adapter; input is internally constructed, not user-supplied arbitrary code. | ai | |
| dependencies | unvetted-dep:@serenity-js/web | AI (dependencies): Sibling monorepo package released at the same version; not an independent third-party dependency. | ai | |
| dependencies | unvetted-dep:@serenity-js/core | AI (dependencies): Sibling monorepo package released at the same version; not an independent third-party dependency. | ai |
Versions (showing 100 of 120)
| Version | Deps | Published |
|---|---|---|
| 3.44.1 | 3 / 16 | |
| 3.44.0 | 3 / 16 | |
| 3.43.4 | 3 / 16 | |
| 3.43.3 | 3 / 16 | |
| 3.43.2 | 3 / 16 | |
| 3.43.1 | 3 / 16 | |
| 3.43.0 | 3 / 16 | |
| 3.42.2 | 3 / 9 | |
| 3.42.1 | 3 / 9 | |
| 3.41.1 | 3 / 9 | |
| 3.40.0 | 3 / 9 | |
| 3.36.0 | 3 / 9 | |
| 3.35.3 | 3 / 9 | |
| 3.35.2 | 3 / 9 | |
| 3.35.1 | 3 / 9 | |
| 3.35.0 | 3 / 9 | |
| 3.34.2 | 3 / 9 | |
| 3.34.1 | 3 / 9 | |
| 3.34.0 | 3 / 9 | |
| 3.33.1 | 3 / 9 | |
| 3.32.5 | 3 / 9 | |
| 3.32.4 | 3 / 9 | |
| 3.32.3 | 3 / 9 | |
| 3.32.2 | 3 / 9 | |
| 3.32.1 | 3 / 9 | |
| 3.32.0 | 3 / 9 | |
| 3.31.17 | 3 / 9 | |
| 3.31.16 | 3 / 9 | |
| 3.31.15 | 3 / 9 | |
| 3.31.14 | 3 / 9 | |
| 3.31.13 | 3 / 9 | |
| 3.31.12 | 3 / 9 | |
| 3.31.10 | 3 / 9 | |
| 3.31.9 | 3 / 9 | |
| 3.31.8 | 3 / 9 | |
| 3.31.7 | 3 / 9 | |
| 3.31.6 | 3 / 9 | |
| 3.31.5 | 3 / 9 | |
| 3.31.4 | 3 / 9 | |
| 3.31.3 | 3 / 9 | |
| 3.31.2 | 3 / 9 | |
| 3.31.1 | 3 / 9 | |
| 3.31.0 | 3 / 9 | |
| 3.30.0 | 3 / 9 | |
| 3.29.5 | 3 / 9 | |
| 3.29.4 | 3 / 9 | |
| 3.29.3 | 3 / 9 | |
| 3.29.2 | 3 / 9 | |
| 3.28.0 | 3 / 9 | |
| 3.27.0 | 3 / 9 | |
| 3.26.1 | 3 / 9 | |
| 3.26.0 | 3 / 9 | |
| 3.25.5 | 3 / 9 | |
| 3.25.4 | 3 / 9 | |
| 3.25.3 | 3 / 9 | |
| 3.25.2 | 4 / 8 | |
| 3.25.1 | 4 / 8 | |
| 3.25.0 | 4 / 8 | |
| 3.24.1 | 4 / 8 | |
| 3.24.0 | 4 / 8 | |
| 3.23.2 | 4 / 8 | |
| 3.23.1 | 4 / 8 | |
| 3.23.0 | 4 / 8 | |
| 3.22.4 | 4 / 8 | |
| 3.22.3 | 4 / 8 | |
| 3.22.2 | 4 / 8 | |
| 3.22.1 | 4 / 8 | |
| 3.22.0 | 4 / 8 | |
| 3.21.2 | 4 / 8 | |
| 3.21.1 | 4 / 8 | |
| 3.21.0 | 4 / 8 | |
| 3.20.0 | 4 / 8 | |
| 3.19.0 | 4 / 8 | |
| 3.18.1 | 4 / 8 | |
| 3.18.0 | 4 / 8 | |
| 3.17.0 | 4 / 8 | |
| 3.16.2 | 4 / 8 | |
| 3.16.1 | 4 / 8 | |
| 3.16.0 | 4 / 8 | |
| 3.15.1 | 4 / 8 | |
| 3.15.0 | 4 / 8 | |
| 3.14.2 | 4 / 8 | |
| 3.14.1 | 4 / 8 | |
| 3.14.0 | 4 / 8 | |
| 3.13.3 | 4 / 8 | |
| 3.13.2 | 4 / 8 | |
| 3.13.1 | 4 / 8 | |
| 3.13.0 | 4 / 8 | |
| 3.12.0 | 4 / 8 | |
| 3.11.1 | 4 / 8 | |
| 3.11.0 | 4 / 8 | |
| 3.10.4 | 4 / 8 | |
| 3.10.3 | 4 / 8 | |
| 3.10.2 | 4 / 8 | |
| 3.10.1 | 4 / 8 | |
| 3.10.0 | 4 / 8 | |
| 3.9.1 | 4 / 8 | |
| 3.9.0 | 4 / 8 | |
| 3.8.0 | 4 / 8 | |
| 3.7.2 | 4 / 8 |
v3.44.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.31.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.31.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.31.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.31.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.29.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.29.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.29.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.29.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.27.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.26.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.25.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.25.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.25.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.25.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.24.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.23.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.22.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.22.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.22.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.21.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.16.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.16.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.14.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.14.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.