@voiceflow/api-sdk
wrapper for creator-api
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): Scoped @voiceflow org package; Levenshtein match to aws-sdk is coincidental, not a squatting attempt. | ai | |
| dependencies | unvetted-dep:@voiceflow/common | AI (dependencies): First-party Voiceflow org dependency; not a third-party unvetted package. | ai | |
| dependencies | unvetted-dep:@voiceflow/base-types | AI (dependencies): First-party Voiceflow org dependency; not a third-party unvetted package. | ai |
Versions (showing 100 of 342)
| Version | Deps | Published |
|---|---|---|
| 3.29.3 | 5 / 2 | |
| 3.28.60 | 5 / 2 | |
| 3.28.57 | 5 / 2 | |
| 3.28.56 | 5 / 2 | |
| 3.28.55 | 5 / 2 | |
| 3.28.54 | 5 / 2 | |
| 3.28.53 | 5 / 2 | |
| 3.28.52 | 5 / 2 | |
| 3.28.51 | 5 / 2 | |
| 3.28.50 | 5 / 2 | |
| 3.28.49 | 5 / 2 | |
| 3.28.48 | 5 / 2 | |
| 3.28.47 | 5 / 2 | |
| 3.28.46 | 5 / 2 | |
| 3.28.45 | 5 / 2 | |
| 3.28.44 | 5 / 2 | |
| 3.28.43 | 5 / 2 | |
| 3.28.42 | 5 / 2 | |
| 3.28.41 | 5 / 2 | |
| 3.28.40 | 5 / 2 | |
| 3.28.39 | 5 / 2 | |
| 3.28.38 | 5 / 2 | |
| 3.28.37 | 5 / 2 | |
| 3.28.36 | 5 / 2 | |
| 3.28.35 | 5 / 2 | |
| 3.28.34 | 5 / 2 | |
| 3.28.33 | 5 / 2 | |
| 3.28.32 | 5 / 2 | |
| 3.28.31 | 5 / 2 | |
| 3.28.30 | 5 / 2 | |
| 3.28.29 | 5 / 2 | |
| 3.28.28 | 5 / 2 | |
| 3.28.27 | 5 / 2 | |
| 3.28.26 | 5 / 2 | |
| 3.28.25 | 5 / 2 | |
| 3.28.24 | 5 / 2 | |
| 3.28.23 | 5 / 2 | |
| 3.28.22 | 5 / 2 | |
| 3.28.21 | 5 / 2 | |
| 3.28.20 | 5 / 2 | |
| 3.28.19 | 5 / 2 | |
| 3.28.18 | 5 / 2 | |
| 3.28.17 | 5 / 2 | |
| 3.28.16 | 5 / 2 | |
| 3.28.15 | 5 / 2 | |
| 3.28.14 | 5 / 2 | |
| 3.28.13 | 5 / 2 | |
| 3.28.12 | 5 / 2 | |
| 3.28.11 | 5 / 2 | |
| 3.28.10 | 5 / 2 | |
| 3.28.9 | 5 / 2 | |
| 3.28.8 | 5 / 2 | |
| 3.28.5 | 5 / 2 | |
| 3.28.4 | 5 / 2 | |
| 3.28.3 | 5 / 2 | |
| 3.28.2 | 5 / 2 | |
| 3.28.1 | 5 / 2 | |
| 3.28.0 | 5 / 2 | |
| 3.27.34 | 5 / 5 | |
| 3.27.33 | 5 / 5 | |
| 3.27.32 | 5 / 5 | |
| 3.27.31 | 5 / 5 | |
| 3.27.30 | 5 / 5 | |
| 3.27.29 | 5 / 5 | |
| 3.27.28 | 5 / 5 | |
| 3.27.27 | 5 / 5 | |
| 3.27.26 | 5 / 5 | |
| 3.27.25 | 5 / 5 | |
| 3.27.24 | 5 / 5 | |
| 3.27.23 | 5 / 5 | |
| 3.27.22 | 5 / 5 | |
| 3.27.21 | 5 / 3 | |
| 3.27.20 | 5 / 3 | |
| 3.27.19 | 5 / 3 | |
| 3.27.18 | 5 / 3 | |
| 3.27.17 | 5 / 3 | |
| 3.27.16 | 5 / 3 | |
| 3.27.15 | 5 / 3 | |
| 3.27.14 | 5 / 3 | |
| 3.27.13 | 5 / 3 | |
| 3.27.12 | 5 / 3 | |
| 3.27.11 | 5 / 3 | |
| 3.27.10 | 5 / 3 | |
| 3.27.9 | 5 / 3 | |
| 3.27.8 | 5 / 3 | |
| 3.27.7 | 5 / 3 | |
| 3.27.6 | 5 / 3 | |
| 3.27.5 | 5 / 3 | |
| 3.27.4 | 5 / 3 | |
| 3.27.3 | 5 / 3 | |
| 3.27.2 | 5 / 3 | |
| 3.27.1 | 5 / 3 | |
| 3.27.0 | 5 / 3 | |
| 3.26.7 | 5 / 3 | |
| 3.26.6 | 5 / 3 | |
| 3.26.5 | 5 / 3 | |
| 3.26.4 | 5 / 3 | |
| 3.26.3 | 5 / 3 | |
| 3.26.2 | 5 / 3 | |
| 3.26.1 | 5 / 3 |
v3.28.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.