@serenity-js/rest
Serenity/JS Screenplay Pattern library for interacting with REST and other HTTP-based services, supporting comprehensive API testing and blended testing 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 first-party Serenity/JS ecosystem dependency used across all versions of this package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @serenity-js/ package; Levenshtein match to 'jest' is a false positive for this established monorepo package. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @serenity-js/ package; Levenshtein match to 'next' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:react | AI (typosquat): Scoped @serenity-js/ package; Levenshtein match to 'react' is a false positive. | ai |
Versions (showing 24 of 124)
| Version | Deps | Published |
|---|---|---|
| 3.9.1 | 2 / 10 | |
| 3.9.0 | 2 / 10 | |
| 3.8.0 | 2 / 10 | |
| 3.7.2 | 2 / 10 | |
| 3.7.1 | 2 / 10 | |
| 3.7.0 | 2 / 10 | |
| 3.6.1 | 2 / 10 | |
| 3.6.0 | 2 / 10 | |
| 3.5.0 | 2 / 10 | |
| 3.4.2 | 2 / 10 | |
| 3.4.1 | 2 / 10 | |
| 3.4.0 | 2 / 10 | |
| 3.3.1 | 2 / 10 | |
| 3.3.0 | 2 / 10 | |
| 3.2.1 | 2 / 10 | |
| 3.2.0 | 2 / 10 | |
| 3.1.6 | 2 / 10 | |
| 3.1.5 | 2 / 10 | |
| 3.1.3 | 2 / 10 | |
| 3.1.2 | 2 / 10 | |
| 3.1.1 | 2 / 10 | |
| 3.1.0 | 2 / 10 | |
| 3.0.1 | 2 / 10 | |
| 3.0.0 | 2 / 10 |
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.
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.