@storybook/store
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to storybook-bot, the official Storybook automation account (12,877 approved versions, 0 rejected). Legitimate org transition. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a deprecated facade/shim package in the Storybook monorepo; tiny payload and minimal README are expected. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Deprecated facade package in Storybook monorepo; empty description is intentional for a shim that re-exports from @storybook/preview-api. | ai |
Versions (showing 10 of 110)
| Version | Deps | Published |
|---|---|---|
| 6.4.10 | 15 / 0 | |
| 6.4.9 | 15 / 0 | |
| 6.4.8 | 15 / 0 | |
| 6.4.7 | 15 / 0 | |
| 6.4.5 | 15 / 0 | |
| 6.4.4 | 15 / 0 | |
| 6.4.3 | 15 / 0 | |
| 6.4.2 | 15 / 0 | |
| 6.4.1 | 15 / 0 | |
| 6.4.0 | 15 / 0 |
v6.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.