@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 — 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 |
|---|---|---|---|---|
| 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 13 of 13)
| 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 |
v3.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.47
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 (effervescentia) than the most recent previously approved version (vf-serviceaccount) on 2025-11-24, but effervescentia 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.32.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.