@storybook/client-api
Storybook Client API
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@storybook/core-events | AI (phantom-deps): Same-org scoped package used indirectly. Legitimate for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared in package.json; used indirectly through utilities. Legitimate for this package. | ai | |
| phantom-deps | phantom-dep:store2 | AI (phantom-deps): Declared in package.json; used indirectly. Legitimate for this package. | ai | |
| phantom-deps | phantom-dep:memoizerific | AI (phantom-deps): Declared in package.json; used indirectly. Legitimate for this package. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Declared in package.json; used indirectly. Legitimate for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/channels | AI (phantom-deps): Same-org scoped package used indirectly through public API. Legitimate for this package. | ai | |
| phantom-deps | phantom-dep:regenerator-runtime | AI (phantom-deps): Known implicit runtime dependency; declared in package.json. Legitimate for this package. | ai | |
| provenance | publisher-changed | AI (provenance): storybook-bot is the official Storybook automation publisher with a strong track record (13196 approved). This reflects a legitimate org-wide migration to bot-based publishing, not a compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a documented deprecated facade/shim package that re-exports from @storybook/preview-api. Tiny payload and minimal README are expected and stable for this package. | ai | |
| dependencies | unvetted-dep:@types/qs | AI (dependencies): @types/qs is a standard TypeScript type definition package for the qs library; its inclusion as a dependency is a known Storybook pattern and poses no security risk. | ai | |
| phantom-deps | phantom-dep:@types/qs | AI (phantom-deps): TypeScript type package declared as dependency for type resolution; not directly imported at runtime. Normal pattern for Storybook packages. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance on npm; published by a highly trusted maintainer with 13,868 approved packages. Absence of provenance is expected for this era. | ai | |
| phantom-deps | phantom-dep:@types/webpack-env | AI (phantom-deps): TypeScript type package for webpack environment globals; loaded by convention, not direct import. Standard for bundler-aware libraries. | ai | |
| phantom-deps | phantom-dep:@storybook/channel-postmessage | AI (phantom-deps): Same-org sibling package; loaded by framework convention rather than direct import. Expected pattern for Storybook ecosystem packages. | ai |
Versions (showing 100 of 244)
| Version | Deps | Published |
|---|---|---|
| 6.4.10 | 20 / 0 | |
| 6.4.9 | 20 / 0 | |
| 6.4.8 | 20 / 0 | |
| 6.4.7 | 20 / 0 | |
| 6.4.5 | 20 / 0 | |
| 6.4.4 | 20 / 0 | |
| 6.4.3 | 20 / 0 | |
| 6.4.2 | 20 / 0 | |
| 6.4.1 | 20 / 0 | |
| 6.4.0 | 20 / 0 | |
| 6.3.13 | 18 / 0 | |
| 6.3.12 | 18 / 0 | |
| 6.3.11 | 18 / 0 | |
| 6.3.10 | 18 / 0 | |
| 6.3.9 | 18 / 0 | |
| 6.3.8 | 18 / 0 | |
| 6.3.7 | 18 / 0 | |
| 6.3.6 | 18 / 0 | |
| 6.3.5 | 18 / 0 | |
| 6.3.4 | 18 / 0 | |
| 6.3.3 | 18 / 0 | |
| 6.3.2 | 18 / 0 | |
| 6.3.1 | 18 / 0 | |
| 6.3.0 | 18 / 0 | |
| 6.2.9 | 18 / 0 | |
| 6.2.8 | 18 / 0 | |
| 6.2.7 | 18 / 0 | |
| 6.2.6 | 18 / 0 | |
| 6.2.5 | 18 / 0 | |
| 6.2.4 | 18 / 0 | |
| 6.2.3 | 18 / 0 | |
| 6.2.2 | 18 / 0 | |
| 6.2.1 | 18 / 0 | |
| 6.2.0 | 18 / 0 | |
| 6.1.21 | 18 / 0 | |
| 6.1.20 | 18 / 0 | |
| 6.1.19 | 18 / 0 | |
| 6.1.18 | 18 / 0 | |
| 6.1.17 | 18 / 0 | |
| 6.1.16 | 18 / 0 | |
| 6.1.15 | 18 / 0 | |
| 6.1.14 | 18 / 0 | |
| 6.1.12 | 18 / 0 | |
| 6.1.11 | 18 / 0 | |
| 6.1.10 | 18 / 0 | |
| 6.1.9 | 18 / 0 | |
| 6.1.8 | 18 / 0 | |
| 6.1.7 | 18 / 0 | |
| 6.1.6 | 18 / 0 | |
| 6.1.5 | 18 / 0 | |
| 6.1.4 | 18 / 0 | |
| 6.1.3 | 18 / 0 | |
| 6.1.2 | 18 / 0 | |
| 6.1.1 | 18 / 0 | |
| 6.1.0 | 18 / 0 | |
| 6.0.28 | 17 / 0 | |
| 6.0.27 | 17 / 0 | |
| 6.0.26 | 17 / 0 | |
| 6.0.25 | 17 / 0 | |
| 6.0.24 | 17 / 0 | |
| 6.0.23 | 17 / 0 | |
| 6.0.22 | 17 / 0 | |
| 6.0.21 | 17 / 0 | |
| 6.0.20 | 17 / 0 | |
| 6.0.19 | 17 / 0 | |
| 6.0.18 | 17 / 0 | |
| 6.0.17 | 17 / 0 | |
| 6.0.16 | 17 / 0 | |
| 6.0.15 | 17 / 0 | |
| 6.0.14 | 17 / 0 | |
| 6.0.13 | 17 / 0 | |
| 6.0.12 | 17 / 0 | |
| 6.0.11 | 17 / 0 | |
| 6.0.10 | 17 / 0 | |
| 6.0.9 | 17 / 0 | |
| 6.0.7 | 17 / 0 | |
| 6.0.6 | 17 / 0 | |
| 6.0.5 | 17 / 0 | |
| 6.0.4 | 17 / 0 | |
| 6.0.3 | 17 / 0 | |
| 6.0.2 | 17 / 0 | |
| 6.0.1 | 17 / 0 | |
| 6.0.0 | 17 / 0 | |
| 5.3.21 | 17 / 0 | |
| 5.3.20 | 17 / 0 | |
| 5.3.19 | 17 / 0 | |
| 5.3.18 | 17 / 0 | |
| 5.3.17 | 17 / 0 | |
| 5.3.15 | 17 / 0 | |
| 5.3.14 | 17 / 0 | |
| 5.3.13 | 17 / 0 | |
| 5.3.12 | 17 / 0 | |
| 5.3.11 | 17 / 0 | |
| 5.3.10 | 17 / 0 | |
| 5.3.9 | 17 / 0 | |
| 5.3.8 | 17 / 0 | |
| 5.3.7 | 16 / 0 | |
| 5.3.6 | 16 / 0 | |
| 5.3.5 | 16 / 0 | |
| 5.3.4 | 16 / 0 |
v6.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.