@storyblok/js
SDK to integrate Storyblok into your project using JavaScript.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @storyblok/js is the official Storyblok JS SDK, not a typosquat of 'qs'. Scoped package name comparison produces spurious Levenshtein matches. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @storyblok/js is the official Storyblok JS SDK, not a typosquat of 'jest'. Spurious Levenshtein match on scoped package name. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @storyblok/js is the official Storyblok JS SDK, not a typosquat of 'pg'. Spurious Levenshtein match on scoped package name. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): @storyblok/js is the official Storyblok JS SDK, not a typosquat of 'rxjs'. Spurious Levenshtein match on scoped package name. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @storyblok/js is the official Storyblok JS SDK, not a typosquat of 'joi'. Spurious Levenshtein match on scoped package name. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @storyblok/js is the official Storyblok JS SDK, not a typosquat of 'ajv'. Spurious Levenshtein match on scoped package name. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 5.1.8 | 2 / 17 | |
| 5.1.7 | 2 / 17 | |
| 5.1.6 | 2 / 17 | |
| 5.1.5 | 2 / 17 | |
| 5.1.4 | 2 / 17 | |
| 5.1.3 | 2 / 17 | |
| 5.1.2 | 2 / 17 | |
| 5.1.1 | 2 / 17 | |
| 5.1.0 | 2 / 17 | |
| 5.0.0 | 2 / 17 | |
| 4.4.5 | 2 / 17 | |
| 4.4.4 | 2 / 17 | |
| 4.4.3 | 2 / 17 | |
| 4.4.2 | 2 / 17 | |
| 4.4.1 | 2 / 17 |
v5.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.3
2 findingsPackage name '@storyblok/js' is 1 edit(s) away from popular package 'qs'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.