@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 20 of 120)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 4 / 8 | |
| 3.7.0 | 4 / 8 | |
| 3.6.1 | 4 / 8 | |
| 3.6.0 | 4 / 8 | |
| 3.5.0 | 4 / 8 | |
| 3.4.2 | 4 / 8 | |
| 3.4.1 | 4 / 8 | |
| 3.4.0 | 4 / 8 | |
| 3.3.1 | 4 / 8 | |
| 3.3.0 | 4 / 8 | |
| 3.2.1 | 4 / 8 | |
| 3.2.0 | 4 / 8 | |
| 3.1.6 | 4 / 8 | |
| 3.1.5 | 4 / 8 | |
| 3.1.3 | 4 / 8 | |
| 3.1.2 | 4 / 8 | |
| 3.1.1 | 4 / 8 | |
| 3.1.0 | 4 / 8 | |
| 3.0.1 | 4 / 8 | |
| 3.0.0 | 4 / 8 |
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.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.