@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 |
|---|---|---|
| 7.6.24 | 2 / 0 | |
| 7.6.23 | 2 / 0 | |
| 7.6.22 | 2 / 0 | |
| 7.6.21 | 2 / 0 | |
| 7.6.20 | 2 / 0 | |
| 7.6.19 | 2 / 0 | |
| 7.6.18 | 2 / 0 | |
| 7.6.17 | 2 / 0 | |
| 7.6.16 | 2 / 0 | |
| 7.6.15 | 2 / 0 | |
| 7.6.14 | 2 / 0 | |
| 7.6.13 | 2 / 0 | |
| 7.6.12 | 2 / 0 | |
| 7.6.11 | 2 / 0 | |
| 7.6.10 | 2 / 0 | |
| 7.6.9 | 2 / 0 | |
| 7.6.8 | 2 / 0 | |
| 7.6.7 | 2 / 0 | |
| 7.6.6 | 2 / 0 | |
| 7.6.5 | 2 / 0 | |
| 7.6.4 | 2 / 0 | |
| 7.6.3 | 2 / 0 | |
| 7.6.2 | 2 / 0 | |
| 7.6.1 | 2 / 0 | |
| 7.6.0 | 2 / 0 | |
| 7.5.3 | 2 / 0 | |
| 7.5.2 | 2 / 0 | |
| 7.5.1 | 2 / 0 | |
| 7.5.0 | 2 / 0 | |
| 7.4.6 | 2 / 0 | |
| 7.4.5 | 2 / 0 | |
| 7.4.4 | 2 / 0 | |
| 7.4.3 | 2 / 0 | |
| 7.4.2 | 2 / 0 | |
| 7.4.1 | 2 / 0 | |
| 7.4.0 | 2 / 0 | |
| 7.3.2 | 2 / 0 | |
| 7.3.1 | 2 / 0 | |
| 7.3.0 | 2 / 0 | |
| 7.2.3 | 2 / 0 | |
| 7.2.2 | 2 / 0 | |
| 7.2.1 | 2 / 0 | |
| 7.2.0 | 2 / 0 | |
| 7.1.1 | 2 / 0 | |
| 7.1.0 | 2 / 0 | |
| 7.0.27 | 2 / 0 | |
| 7.0.26 | 2 / 0 | |
| 7.0.25 | 2 / 0 | |
| 7.0.24 | 2 / 0 | |
| 7.0.23 | 2 / 0 | |
| 7.0.22 | 2 / 0 | |
| 7.0.21 | 2 / 0 | |
| 7.0.20 | 2 / 0 | |
| 7.0.19 | 2 / 0 | |
| 7.0.18 | 2 / 0 | |
| 7.0.17 | 2 / 0 | |
| 7.0.16 | 2 / 0 | |
| 7.0.15 | 2 / 0 | |
| 7.0.14 | 2 / 0 | |
| 7.0.13 | 2 / 0 | |
| 7.0.12 | 2 / 0 | |
| 7.0.11 | 2 / 0 | |
| 7.0.10 | 2 / 0 | |
| 7.0.9 | 2 / 0 | |
| 7.0.8 | 2 / 0 | |
| 7.0.7 | 2 / 0 | |
| 7.0.6 | 2 / 0 | |
| 7.0.5 | 2 / 0 | |
| 7.0.4 | 2 / 0 | |
| 7.0.3 | 2 / 0 | |
| 7.0.2 | 2 / 0 | |
| 7.0.1 | 2 / 0 | |
| 7.0.0 | 2 / 0 | |
| 6.5.16 | 20 / 0 | |
| 6.5.15 | 20 / 0 | |
| 6.5.14 | 20 / 0 | |
| 6.5.13 | 20 / 0 | |
| 6.5.12 | 20 / 0 | |
| 6.5.11 | 20 / 0 | |
| 6.5.10 | 20 / 0 | |
| 6.5.9 | 20 / 0 | |
| 6.5.8 | 20 / 0 | |
| 6.5.7 | 20 / 0 | |
| 6.5.6 | 20 / 0 | |
| 6.5.5 | 20 / 0 | |
| 6.5.4 | 20 / 0 | |
| 6.5.3 | 20 / 0 | |
| 6.5.2 | 20 / 0 | |
| 6.5.0 | 20 / 0 | |
| 6.4.22 | 20 / 0 | |
| 6.4.21 | 20 / 0 | |
| 6.4.20 | 20 / 0 | |
| 6.4.19 | 20 / 0 | |
| 6.4.18 | 20 / 0 | |
| 6.4.17 | 20 / 0 | |
| 6.4.16 | 20 / 0 | |
| 6.4.15 | 20 / 0 | |
| 6.4.14 | 20 / 0 | |
| 6.4.13 | 20 / 0 | |
| 6.4.12 | 20 / 0 |
v7.6.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.21
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.20
2 findingsThis version was published by a different npm account than previous versions on 2024-06-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.18
2 findingsThis version was published by a different npm account than previous versions on 2024-04-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.0.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v6.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.5.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.4.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.