@voiceflow/vite-config
vite config for voiceflow
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): effervescentia is an established Voiceflow org maintainer with 149 approved packages; transition from service account is expected. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Voiceflow org internal team rotation; publisher remains vf-serviceaccount with strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Part of same org-internal rotation; no signs of hostile takeover. | ai | |
| phantom-deps | phantom-dep:@svgr/plugin-jsx | AI (phantom-deps): Config package re-exports plugins by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:vite-plugin-html | AI (phantom-deps): Config package re-exports plugins by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config package re-exports plugins by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-replace | AI (phantom-deps): Framework-scoped package loaded by convention in a vite config wrapper. | ai | |
| phantom-deps | phantom-dep:@svgr/babel-plugin-transform-svg-component | AI (phantom-deps): Config package re-exports plugins by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@svgr/plugin-svgo | AI (phantom-deps): Config package re-exports plugins by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@svgr/core | AI (phantom-deps): Config package re-exports plugins by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:git-branch | AI (phantom-deps): Config package re-exports plugins by convention; not directly imported by design. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.12.1 | 4 / 3 | |
| 2.12.0 | 5 / 3 | |
| 2.11.0 | 7 / 3 | |
| 2.10.1 | 7 / 3 | |
| 2.10.0 | 7 / 3 | |
| 2.9.1 | 15 / 4 | |
| 2.9.0 | 15 / 6 | |
| 2.8.3 | 15 / 6 | |
| 2.8.2 | 15 / 6 | |
| 2.8.1 | 15 / 6 | |
| 2.8.0 | 15 / 6 | |
| 2.7.2 | 14 / 5 | |
| 2.7.1 | 14 / 5 | |
| 2.7.0 | 14 / 5 | |
| 2.6.4 | 14 / 5 | |
| 2.6.1 | 14 / 5 | |
| 2.6.0 | 14 / 5 | |
| 2.5.0 | 14 / 5 | |
| 2.4.2 | 14 / 5 |
v2.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
2 findingsThis version was published by a different npm account than previous versions on 2025-11-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.