@storybook/ui
Core Storybook UI
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:history | AI (phantom-deps): Phantom dependency is legitimate for this package; likely used transitively through @storybook/* dependencies. | ai | |
| phantom-deps | phantom-dep:react-lifecycles-compat | AI (phantom-deps): Phantom dependency is legitimate; used for React compatibility through transitive dependencies. | ai | |
| phantom-deps | phantom-dep:lodash.throttle | AI (phantom-deps): Phantom dependency is legitimate; used in event handling through transitive dependencies. | ai | |
| phantom-deps | phantom-dep:lodash.sortby | AI (phantom-deps): Phantom dependency is legitimate; used in data processing through transitive dependencies. | ai | |
| phantom-deps | phantom-dep:react-modal | AI (phantom-deps): Phantom dependency is legitimate; used in modal UI components through transitive dependencies. | ai | |
| phantom-deps | phantom-dep:keycode | AI (phantom-deps): Phantom dependency is legitimate; used in UI event handling through transitive dependencies. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): Declared in package.json; phantom-dep pattern is expected for Storybook monorepo packages. | ai | |
| phantom-deps | phantom-dep:telejson | AI (phantom-deps): Declared in package.json; phantom-dep pattern is expected for Storybook monorepo packages. | ai | |
| phantom-deps | phantom-dep:util-deprecate | AI (phantom-deps): Declared in package.json; phantom-dep pattern is expected for Storybook monorepo packages. | ai | |
| phantom-deps | phantom-dep:emotion-theming | AI (phantom-deps): Declared in package.json; phantom-dep pattern is expected for Storybook monorepo packages. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Declared in package.json; phantom-dep pattern is expected for Storybook monorepo packages. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @storybook/ui is a scoped package in the official Storybook org; Levenshtein comparison to 'uuid' is a false positive with no plausible confusion. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @storybook/ui is a scoped package in the official Storybook org; Levenshtein comparison to 'qs' is a false positive with no plausible confusion. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @storybook/ui is a scoped package in the official Storybook org; Levenshtein comparison to 'joi' is a false positive with no plausible confusion. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @storybook/ui is a scoped package in the official Storybook org; Levenshtein comparison to 'yup' is a false positive with no plausible confusion. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @storybook/ui is a scoped package in the official Storybook org; Levenshtein comparison to 'pg' is a false positive with no plausible confusion. | ai | |
| phantom-deps | phantom-dep:core-js-pure | AI (phantom-deps): core-js-pure is a declared runtime dep used as part of Storybook's polyfill strategy; phantom detection is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/markdown-to-jsx | AI (phantom-deps): Type definitions declared as runtime dep for framework convention loading; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/channels | AI (phantom-deps): Same-org Storybook package declared as a runtime dep; phantom detection is a false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@emotion/core | AI (phantom-deps): @emotion/core is a declared dep referenced in config/build files; standard for Storybook's theming/emotion setup. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance support; trusted publisher with strong track record. Not a risk signal for this package. | ai |
Versions (showing 100 of 244)
| Version | Deps | Published |
|---|---|---|
| 6.0.10 | 31 / 11 | |
| 6.0.9 | 31 / 11 | |
| 6.0.7 | 31 / 11 | |
| 6.0.6 | 31 / 11 | |
| 6.0.5 | 31 / 11 | |
| 6.0.4 | 31 / 11 | |
| 6.0.3 | 31 / 11 | |
| 6.0.2 | 31 / 11 | |
| 6.0.1 | 31 / 11 | |
| 6.0.0 | 31 / 11 | |
| 5.3.21 | 34 / 6 | |
| 5.3.20 | 34 / 6 | |
| 5.3.19 | 34 / 6 | |
| 5.3.18 | 34 / 6 | |
| 5.3.17 | 34 / 6 | |
| 5.3.15 | 34 / 6 | |
| 5.3.14 | 34 / 6 | |
| 5.3.13 | 34 / 6 | |
| 5.3.12 | 34 / 6 | |
| 5.3.11 | 34 / 6 | |
| 5.3.10 | 34 / 6 | |
| 5.3.9 | 34 / 6 | |
| 5.3.8 | 34 / 6 | |
| 5.3.7 | 34 / 6 | |
| 5.3.6 | 34 / 6 | |
| 5.3.5 | 34 / 6 | |
| 5.3.4 | 34 / 6 | |
| 5.3.3 | 34 / 6 | |
| 5.3.2 | 34 / 6 | |
| 5.3.1 | 34 / 6 | |
| 5.3.0 | 34 / 6 | |
| 5.2.8 | 33 / 6 | |
| 5.2.7 | 33 / 6 | |
| 5.2.6 | 33 / 6 | |
| 5.2.5 | 33 / 6 | |
| 5.2.4 | 33 / 6 | |
| 5.2.3 | 33 / 6 | |
| 5.2.2 | 33 / 6 | |
| 5.2.1 | 35 / 4 | |
| 5.2.0 | 35 / 4 | |
| 5.1.11 | 34 / 4 | |
| 5.1.10 | 34 / 4 | |
| 5.1.9 | 34 / 4 | |
| 5.1.8 | 31 / 4 | |
| 5.1.7 | 31 / 4 | |
| 5.1.5 | 31 / 4 | |
| 5.1.4 | 31 / 4 | |
| 5.1.3 | 31 / 3 | |
| 5.1.1 | 31 / 3 | |
| 5.0.11 | 35 / 2 | |
| 5.0.10 | 35 / 2 | |
| 5.0.9 | 35 / 2 | |
| 5.0.8 | 35 / 2 | |
| 5.0.7 | 35 / 2 | |
| 5.0.6 | 35 / 2 | |
| 5.0.5 | 35 / 2 | |
| 5.0.4 | 35 / 2 | |
| 5.0.3 | 35 / 2 | |
| 5.0.2 | 35 / 2 | |
| 5.0.1 | 35 / 2 | |
| 5.0.0 | 34 / 2 | |
| 4.1.18 | 22 / 2 | |
| 4.1.17 | 22 / 2 | |
| 4.1.16 | 22 / 2 | |
| 4.1.14 | 22 / 2 | |
| 4.1.13 | 22 / 2 | |
| 4.1.12 | 22 / 2 | |
| 4.1.11 | 22 / 2 | |
| 4.1.10 | 22 / 2 | |
| 4.1.9 | 22 / 2 | |
| 4.1.8 | 22 / 2 | |
| 4.1.7 | 22 / 2 | |
| 4.1.6 | 22 / 2 | |
| 4.1.5 | 22 / 2 | |
| 4.1.4 | 20 / 2 | |
| 4.1.3 | 20 / 2 | |
| 4.1.2 | 20 / 2 | |
| 4.1.1 | 20 / 2 | |
| 4.1.0 | 20 / 2 | |
| 4.0.12 | 20 / 2 | |
| 4.0.11 | 20 / 2 | |
| 4.0.10 | 20 / 2 | |
| 4.0.9 | 20 / 2 | |
| 4.0.8 | 20 / 2 | |
| 4.0.7 | 20 / 2 | |
| 4.0.6 | 20 / 2 | |
| 4.0.4 | 20 / 2 | |
| 4.0.3 | 20 / 2 | |
| 4.0.2 | 20 / 2 | |
| 4.0.1 | 20 / 2 | |
| 4.0.0 | 20 / 2 | |
| 3.4.12 | 21 / 2 | |
| 3.4.11 | 21 / 2 | |
| 3.4.10 | 21 / 2 | |
| 3.4.8 | 21 / 2 | |
| 3.4.7 | 21 / 2 | |
| 3.4.6 | 21 / 2 | |
| 3.4.5 | 21 / 2 | |
| 3.4.4 | 21 / 2 | |
| 3.4.3 | 21 / 2 |
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.
v5.3.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.
v5.3.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.
v5.3.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.
v5.3.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.
v5.3.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.
v5.3.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.
v5.3.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.2.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.
v5.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.