@voiceflow/voiceflow-types
Voiceflow 'voiceflow' project types
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Voiceflow org rotates maintainers internally; consistent with team changes across their package ecosystem. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same internal rotation pattern; no malicious indicators present. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Voiceflow monorepo with 318 versions; gaps in publish cadence are normal for type-only packages. | ai | |
| dependencies | unvetted-dep:@voiceflow/base-types | AI (dependencies): Internal Voiceflow sibling package; expected dependency for this org's type library. | ai | |
| dependencies | unvetted-dep:@voiceflow/chat-types | AI (dependencies): Internal Voiceflow sibling package; expected dependency for this org's type library. | ai | |
| dependencies | unvetted-dep:@voiceflow/voice-types | AI (dependencies): Internal Voiceflow sibling package; expected dependency for this org's type library. | ai |
Versions (showing 100 of 317)
| Version | Deps | Published |
|---|---|---|
| 3.33.3 | 3 / 0 | |
| 3.33.2 | 3 / 0 | |
| 3.33.1 | 3 / 0 | |
| 3.33.0 | 3 / 0 | |
| 3.32.47 | 3 / 0 | |
| 3.32.44 | 3 / 0 | |
| 3.32.43 | 3 / 0 | |
| 3.32.42 | 3 / 0 | |
| 3.32.41 | 3 / 0 | |
| 3.32.40 | 3 / 0 | |
| 3.32.39 | 3 / 0 | |
| 3.32.38 | 3 / 0 | |
| 3.32.37 | 3 / 0 | |
| 3.32.36 | 3 / 0 | |
| 3.32.35 | 3 / 0 | |
| 3.32.34 | 3 / 0 | |
| 3.32.33 | 3 / 0 | |
| 3.32.32 | 3 / 0 | |
| 3.32.31 | 3 / 0 | |
| 3.32.30 | 3 / 0 | |
| 3.32.29 | 3 / 0 | |
| 3.32.28 | 3 / 0 | |
| 3.32.27 | 3 / 0 | |
| 3.32.26 | 3 / 0 | |
| 3.32.25 | 3 / 0 | |
| 3.32.24 | 3 / 0 | |
| 3.32.23 | 3 / 0 | |
| 3.32.22 | 3 / 0 | |
| 3.32.21 | 3 / 0 | |
| 3.32.20 | 3 / 0 | |
| 3.32.19 | 3 / 0 | |
| 3.32.18 | 3 / 0 | |
| 3.32.17 | 3 / 0 | |
| 3.32.16 | 3 / 0 | |
| 3.32.15 | 3 / 0 | |
| 3.32.14 | 3 / 0 | |
| 3.32.13 | 3 / 0 | |
| 3.32.12 | 3 / 0 | |
| 3.32.11 | 3 / 0 | |
| 3.32.10 | 3 / 0 | |
| 3.32.9 | 3 / 0 | |
| 3.32.8 | 3 / 0 | |
| 3.32.7 | 3 / 0 | |
| 3.32.6 | 3 / 0 | |
| 3.32.5 | 3 / 0 | |
| 3.32.4 | 3 / 0 | |
| 3.32.3 | 3 / 0 | |
| 3.32.2 | 3 / 0 | |
| 3.32.1 | 3 / 0 | |
| 3.32.0 | 3 / 0 | |
| 3.31.8 | 3 / 0 | |
| 3.31.7 | 3 / 0 | |
| 3.31.6 | 3 / 0 | |
| 3.31.5 | 3 / 0 | |
| 3.31.4 | 3 / 0 | |
| 3.31.3 | 3 / 0 | |
| 3.31.1 | 3 / 0 | |
| 3.30.5 | 3 / 0 | |
| 3.30.4 | 3 / 0 | |
| 3.30.3 | 3 / 0 | |
| 3.30.2 | 3 / 0 | |
| 3.30.1 | 3 / 0 | |
| 3.30.0 | 3 / 0 | |
| 3.29.0 | 3 / 1 | |
| 3.28.4 | 3 / 1 | |
| 3.28.3 | 3 / 1 | |
| 3.28.2 | 3 / 1 | |
| 3.28.1 | 3 / 1 | |
| 3.28.0 | 3 / 1 | |
| 3.27.0 | 3 / 1 | |
| 3.26.45 | 3 / 1 | |
| 3.26.44 | 3 / 1 | |
| 3.26.43 | 3 / 1 | |
| 3.26.42 | 3 / 1 | |
| 3.26.41 | 3 / 1 | |
| 3.26.40 | 3 / 1 | |
| 3.26.39 | 3 / 1 | |
| 3.26.38 | 3 / 1 | |
| 3.26.37 | 3 / 1 | |
| 3.26.36 | 3 / 0 | |
| 3.26.35 | 3 / 0 | |
| 3.26.34 | 3 / 0 | |
| 3.26.33 | 3 / 0 | |
| 3.26.32 | 3 / 0 | |
| 3.26.31 | 3 / 0 | |
| 3.26.30 | 3 / 0 | |
| 3.26.29 | 3 / 0 | |
| 3.26.28 | 3 / 0 | |
| 3.26.27 | 3 / 0 | |
| 3.26.26 | 3 / 0 | |
| 3.26.25 | 3 / 0 | |
| 3.26.24 | 3 / 0 | |
| 3.26.23 | 3 / 0 | |
| 3.26.22 | 3 / 0 | |
| 3.26.21 | 3 / 0 | |
| 3.26.20 | 3 / 0 | |
| 3.26.19 | 3 / 0 | |
| 3.26.18 | 3 / 0 | |
| 3.26.17 | 3 / 0 | |
| 3.26.16 | 3 / 0 |
v3.32.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vf-serviceaccount) than the most recent previously approved version (denyslinkov) on 2024-06-20, but vf-serviceaccount is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.31.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (denyslinkov) than the most recent previously approved version (vf-serviceaccount) on 2024-06-12, but denyslinkov is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.30.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.