@serenity-js/web
Serenity/JS Screenplay Pattern library offering a flexible, web driver-agnostic approach for interacting with web-based user interfaces and components, suitable for various testing contexts
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): Stable, well-known dependency of serenity-js ecosystem; not a risk signal. | ai | |
| dependencies | unvetted-dep:@serenity-js/core | AI (dependencies): Sibling monorepo package; co-released at same version, expected dependency. | ai | |
| dependencies | unvetted-dep:@serenity-js/assertions | AI (dependencies): Sibling monorepo package; co-released at same version, expected dependency. | ai |
Versions (showing 16 of 116)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 3 / 8 | |
| 3.4.2 | 3 / 8 | |
| 3.4.1 | 3 / 8 | |
| 3.4.0 | 3 / 8 | |
| 3.3.1 | 3 / 8 | |
| 3.3.0 | 3 / 8 | |
| 3.2.1 | 3 / 8 | |
| 3.2.0 | 3 / 8 | |
| 3.1.6 | 3 / 8 | |
| 3.1.5 | 3 / 8 | |
| 3.1.3 | 3 / 8 | |
| 3.1.2 | 3 / 8 | |
| 3.1.1 | 3 / 8 | |
| 3.1.0 | 3 / 8 | |
| 3.0.1 | 3 / 8 | |
| 3.0.0 | 3 / 8 |
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.