@voiceflow/sdk-runtime
An SDK for interacting with the Voiceflow runtime.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@voiceflow/fetch | AI (dependencies): First-party Voiceflow package; same org as publisher, stable pattern across versions. | ai |
Versions (showing 100 of 123)
| Version | Deps | Published |
|---|---|---|
| 1.75.0 | 4 / 2 | |
| 1.74.0 | 4 / 2 | |
| 1.73.0 | 4 / 2 | |
| 1.72.0 | 4 / 2 | |
| 1.71.0 | 4 / 2 | |
| 1.70.0 | 4 / 2 | |
| 1.69.1 | 4 / 2 | |
| 1.69.0 | 4 / 2 | |
| 1.68.0 | 4 / 2 | |
| 1.67.0 | 4 / 2 | |
| 1.66.0 | 4 / 2 | |
| 1.65.0 | 4 / 2 | |
| 1.64.0 | 4 / 2 | |
| 1.63.0 | 4 / 2 | |
| 1.62.0 | 4 / 2 | |
| 1.61.0 | 4 / 2 | |
| 1.60.1 | 4 / 2 | |
| 1.60.0 | 4 / 2 | |
| 1.59.0 | 4 / 2 | |
| 1.58.0 | 4 / 2 | |
| 1.57.0 | 4 / 2 | |
| 1.56.0 | 4 / 2 | |
| 1.55.0 | 4 / 2 | |
| 1.54.0 | 4 / 2 | |
| 1.53.0 | 4 / 2 | |
| 1.52.0 | 4 / 2 | |
| 1.51.1 | 4 / 2 | |
| 1.51.0 | 4 / 2 | |
| 1.50.4 | 4 / 2 | |
| 1.50.3 | 4 / 2 | |
| 1.50.2 | 4 / 2 | |
| 1.50.1 | 4 / 2 | |
| 1.50.0 | 4 / 2 | |
| 1.49.1 | 4 / 2 | |
| 1.49.0 | 4 / 2 | |
| 1.48.0 | 4 / 2 | |
| 1.47.0 | 4 / 2 | |
| 1.46.0 | 4 / 2 | |
| 1.45.0 | 4 / 2 | |
| 1.44.2 | 4 / 2 | |
| 1.44.1 | 4 / 2 | |
| 1.44.0 | 4 / 2 | |
| 1.43.0 | 4 / 2 | |
| 1.42.1 | 4 / 2 | |
| 1.42.0 | 4 / 2 | |
| 1.41.2 | 4 / 2 | |
| 1.41.1 | 4 / 2 | |
| 1.41.0 | 4 / 2 | |
| 1.40.2 | 4 / 2 | |
| 1.40.1 | 4 / 2 | |
| 1.40.0 | 4 / 2 | |
| 1.39.0 | 4 / 2 | |
| 1.38.1 | 4 / 2 | |
| 1.27.0 | 3 / 1 | |
| 1.26.0 | 3 / 1 | |
| 1.25.1 | 3 / 1 | |
| 1.25.0 | 3 / 1 | |
| 1.24.0 | 3 / 1 | |
| 1.23.0 | 3 / 1 | |
| 1.22.0 | 3 / 1 | |
| 1.21.0 | 3 / 1 | |
| 1.20.0 | 3 / 1 | |
| 1.19.0 | 3 / 1 | |
| 1.18.1 | 3 / 1 | |
| 1.18.0 | 3 / 1 | |
| 1.17.4 | 3 / 1 | |
| 1.17.3 | 3 / 1 | |
| 1.17.2 | 3 / 1 | |
| 1.17.1 | 3 / 1 | |
| 1.17.0 | 3 / 1 | |
| 1.16.1 | 3 / 1 | |
| 1.16.0 | 3 / 1 | |
| 1.15.0 | 3 / 1 | |
| 1.14.1 | 3 / 1 | |
| 1.13.1 | 3 / 1 | |
| 1.13.0 | 3 / 1 | |
| 1.12.1 | 3 / 1 | |
| 1.12.0 | 3 / 1 | |
| 1.11.0 | 2 / 1 | |
| 1.10.0 | 2 / 1 | |
| 1.9.0 | 2 / 1 | |
| 1.8.2 | 2 / 1 | |
| 1.8.1 | 2 / 1 | |
| 1.8.0 | 2 / 1 | |
| 1.7.0 | 2 / 4 | |
| 1.6.0 | 2 / 4 | |
| 1.5.28 | 2 / 4 | |
| 1.5.27 | 2 / 4 | |
| 1.5.26 | 2 / 4 | |
| 1.5.25 | 2 / 4 | |
| 1.5.24 | 2 / 4 | |
| 1.5.23 | 2 / 4 | |
| 1.5.22 | 2 / 4 | |
| 1.5.21 | 2 / 4 | |
| 1.5.20 | 2 / 4 | |
| 1.5.19 | 2 / 4 | |
| 1.5.18 | 2 / 4 | |
| 1.5.17 | 2 / 4 | |
| 1.5.16 | 2 / 4 | |
| 1.5.15 | 2 / 4 |
v1.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.