@serenity-js/assertions
Serenity/JS universal assertion library supporting all types of functional tests, including both web and REST API 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 stable, long-standing dependency of serenity-js packages; not a risk. | ai | |
| dependencies | unvetted-dep:@serenity-js/core | AI (dependencies): Sibling monorepo package; expected dependency for all @serenity-js/* packages. | ai |
Versions (showing 16 of 116)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 2 / 8 | |
| 3.4.2 | 2 / 8 | |
| 3.4.1 | 2 / 8 | |
| 3.4.0 | 2 / 8 | |
| 3.3.1 | 2 / 8 | |
| 3.3.0 | 2 / 8 | |
| 3.2.1 | 2 / 8 | |
| 3.2.0 | 2 / 8 | |
| 3.1.6 | 2 / 8 | |
| 3.1.5 | 2 / 8 | |
| 3.1.3 | 2 / 8 | |
| 3.1.2 | 2 / 8 | |
| 3.1.1 | 2 / 8 | |
| 3.1.0 | 2 / 8 | |
| 3.0.1 | 2 / 8 | |
| 3.0.0 | 2 / 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.