@voiceflow/storybook-config
## Install
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): vf-serviceaccount is Voiceflow's org CI account with strong track record; consistent with internal publisher consolidation. | ai | |
| phantom-deps | phantom-dep:@storybook/cli | AI (phantom-deps): Storybook config package; deps are re-exported/configured, not directly imported. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@storybook/types | AI (phantom-deps): Storybook config packages reference addons in config files without direct TS imports; stable false positive. | ai | |
| phantom-deps | phantom-dep:storybook-dark-mode | AI (phantom-deps): Storybook addon referenced in config, not imported directly; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-links | AI (phantom-deps): Storybook addon referenced in config, not imported directly; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:storybook-addon-pseudo-states | AI (phantom-deps): Storybook addon referenced in config, not imported directly; expected pattern for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.6.0 | 5 / 2 | |
| 1.5.2 | 5 / 2 | |
| 1.5.1 | 5 / 2 | |
| 1.5.0 | 4 / 2 | |
| 1.4.1 | 6 / 2 | |
| 1.4.0 | 6 / 2 | |
| 1.3.1 | 6 / 2 | |
| 1.3.0 | 6 / 2 | |
| 1.2.4 | 6 / 2 | |
| 1.2.1 | 6 / 2 | |
| 1.2.0 | 6 / 2 |
v1.6.0
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.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.
v1.4.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. 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.
v1.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-22. 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.
v1.3.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. 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.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-25. 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.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.