@voiceflow/fetch
Voiceflow fetch wrapper and error handling for SDKs
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): vf-serviceaccount is Voiceflow's org CI account with strong approval track record; transition from individual to service account is expected. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 0 / 5 | |
| 1.14.1 | 0 / 5 | |
| 1.14.0 | 0 / 5 | |
| 1.13.0 | 0 / 5 | |
| 1.12.6 | 0 / 5 | |
| 1.12.5 | 0 / 5 | |
| 1.12.4 | 0 / 5 | |
| 1.12.3 | 0 / 5 | |
| 1.12.2 | 0 / 5 | |
| 1.12.1 | 0 / 5 | |
| 1.12.0 | 0 / 5 | |
| 1.11.3 | 0 / 5 | |
| 1.11.0 | 0 / 5 | |
| 1.10.2 | 0 / 5 | |
| 1.10.1 | 0 / 5 | |
| 1.10.0 | 0 / 5 | |
| 1.9.3 | 0 / 5 | |
| 1.9.2 | 0 / 7 | |
| 1.9.1 | 0 / 7 | |
| 1.9.0 | 0 / 7 | |
| 1.8.0 | 0 / 7 | |
| 1.7.0 | 0 / 6 | |
| 1.6.1 | 0 / 6 | |
| 1.6.0 | 0 / 6 | |
| 1.5.5 | 0 / 7 | |
| 1.5.4 | 0 / 7 | |
| 1.5.3 | 0 / 3 | |
| 1.5.2 | 0 / 3 | |
| 1.5.1 | 0 / 3 | |
| 1.5.0 | 0 / 3 | |
| 1.4.0 | 0 / 3 | |
| 1.3.0 | 0 / 3 | |
| 1.2.0 | 0 / 3 | |
| 1.1.0 | 0 / 3 |
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.