@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 — the axios compromise (March 2026) relied on exactly this gap.
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 10 of 10)
| 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 |
v3.28.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.