@storybook/components
Core Storybook Components
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Storybook monorepo publishes many packages simultaneously via CI/CD; rapid successive publishes are expected and normal for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects bundling of highlight.js language modules into the package. Diff is against a different major version (v8.x); size growth is expected and legitimate. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large file count is due to bundled highlight.js language definitions — a legitimate architectural choice for a syntax-highlighting UI component library. | ai | |
| source-diff | obfuscated-file:dist/autoit-A2P2SZ3Z.mjs | AI (source-diff): Bundled highlight.js AutoIt language definition. Minified built-in function lists trigger the rule; content is clearly legitimate. | ai | |
| source-diff | obfuscated-file:dist/armasm-RILIBSME.mjs | AI (source-diff): Bundled highlight.js ARM Assembly language definition. Minified register/directive lists trigger long-line detection; not malicious. | ai | |
| source-diff | obfuscated-file:dist/arduino-V4RV6FJL.mjs | AI (source-diff): Bundled highlight.js Arduino/C++ language definition. Minified keyword/type lists trigger the rule; content is clearly legitimate. | ai | |
| source-diff | obfuscated-file:dist/arcade-CALPTLOT.mjs | AI (source-diff): Bundled highlight.js Arcade language definition. Minified built-in function lists trigger long-line detection; not malicious. | ai | |
| source-diff | obfuscated-file:dist/applescript-7EA7Y3L2.mjs | AI (source-diff): Bundled highlight.js AppleScript language definition. Minification of keyword/pattern arrays triggers the rule; content is clearly legitimate. | ai | |
| source-diff | obfuscated-file:dist/1c-ZTBIS4WH.mjs | AI (source-diff): Bundled highlight.js language definition (1C language). Minified keyword lists trigger long-line detection; not malicious obfuscation. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-dialog | AI (dependencies): @radix-ui/react-dialog is a reputable, widely-used UI primitives library; its use in Storybook UI components is expected and benign across all versions. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-toolbar | AI (phantom-deps): Declared in package.json dependencies; phantom detection is a false positive for bundled packages. | ai | |
| provenance | no-provenance | AI (provenance): Storybook 7.x predates widespread provenance adoption; absence is expected for this version line and not a security concern given the established publisher track record. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-select | AI (phantom-deps): Declared in package.json dependencies; phantom detection is a false positive for bundled packages. | ai | |
| phantom-deps | phantom-dep:util-deprecate | AI (phantom-deps): Declared in package.json dependencies; phantom detection is a false positive for bundled packages where direct import tracing may not reflect actual usage. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-select | AI (dependencies): @radix-ui/react-select is a well-known, widely-used UI primitives library; legitimate dependency for a UI component package like @storybook/components. | ai | |
| phantom-deps | phantom-dep:react-focus-lock | AI (phantom-deps): Legitimately declared dependency used in components; phantom-dep false positive for component libraries. | ai | |
| phantom-deps | phantom-dep:@types/react-syntax-highlighter | AI (phantom-deps): @types package for declared dependency; framework-scoped types loaded by convention in TypeScript projects. | ai | |
| phantom-deps | phantom-dep:@types/react-textarea-autosize | AI (phantom-deps): @types package for declared dependency; framework-scoped types loaded by convention in TypeScript projects. | ai | |
| phantom-deps | phantom-dep:react-helmet-async | AI (phantom-deps): Legitimately declared dependency used in components; phantom-dep false positive for component libraries. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is legitimately declared and used in a React component library; phantom-dep false positive for monorepo/component packages. | ai |
Versions (showing 100 of 401)
| Version | Deps | Published |
|---|---|---|
| 7.6.1 | 10 / 13 | |
| 7.6.0 | 10 / 13 | |
| 7.5.3 | 10 / 14 | |
| 7.5.2 | 10 / 14 | |
| 7.5.1 | 10 / 14 | |
| 7.5.0 | 10 / 14 | |
| 7.4.6 | 10 / 14 | |
| 7.4.5 | 10 / 14 | |
| 7.4.4 | 10 / 14 | |
| 7.4.3 | 10 / 14 | |
| 7.4.2 | 10 / 14 | |
| 7.4.1 | 10 / 14 | |
| 7.4.0 | 10 / 14 | |
| 7.3.2 | 11 / 13 | |
| 7.3.1 | 11 / 13 | |
| 7.3.0 | 11 / 13 | |
| 7.2.3 | 10 / 13 | |
| 7.2.2 | 10 / 13 | |
| 7.2.1 | 10 / 13 | |
| 7.2.0 | 9 / 13 | |
| 7.1.1 | 8 / 13 | |
| 7.1.0 | 8 / 13 | |
| 7.0.27 | 8 / 13 | |
| 7.0.26 | 8 / 13 | |
| 7.0.25 | 8 / 13 | |
| 7.0.24 | 8 / 13 | |
| 7.0.23 | 8 / 13 | |
| 7.0.22 | 8 / 13 | |
| 7.0.21 | 8 / 13 | |
| 7.0.20 | 8 / 13 | |
| 7.0.19 | 8 / 13 | |
| 7.0.18 | 8 / 13 | |
| 7.0.17 | 8 / 13 | |
| 7.0.16 | 8 / 13 | |
| 7.0.15 | 8 / 13 | |
| 7.0.14 | 8 / 13 | |
| 7.0.13 | 8 / 13 | |
| 7.0.12 | 8 / 13 | |
| 7.0.11 | 8 / 13 | |
| 7.0.10 | 8 / 13 | |
| 7.0.9 | 8 / 13 | |
| 7.0.8 | 8 / 13 | |
| 7.0.7 | 8 / 13 | |
| 7.0.6 | 8 / 13 | |
| 7.0.5 | 8 / 13 | |
| 7.0.4 | 8 / 13 | |
| 7.0.3 | 8 / 13 | |
| 7.0.2 | 8 / 13 | |
| 7.0.1 | 8 / 13 | |
| 7.0.0 | 8 / 13 | |
| 6.5.16 | 8 / 21 | |
| 6.5.15 | 8 / 21 | |
| 6.5.14 | 8 / 21 | |
| 6.5.13 | 8 / 21 | |
| 6.5.12 | 8 / 21 | |
| 6.5.11 | 8 / 21 | |
| 6.5.10 | 8 / 21 | |
| 6.5.9 | 10 / 19 | |
| 6.5.8 | 9 / 20 | |
| 6.5.7 | 9 / 20 | |
| 6.5.6 | 9 / 20 | |
| 6.5.5 | 9 / 20 | |
| 6.5.4 | 9 / 20 | |
| 6.5.3 | 9 / 20 | |
| 6.5.2 | 9 / 20 | |
| 6.5.0 | 9 / 20 | |
| 6.4.22 | 24 / 2 | |
| 6.4.21 | 24 / 2 | |
| 6.4.20 | 24 / 2 | |
| 6.4.19 | 24 / 2 | |
| 6.4.18 | 24 / 2 | |
| 6.4.17 | 24 / 2 | |
| 6.4.16 | 24 / 2 | |
| 6.4.15 | 24 / 2 | |
| 6.4.14 | 24 / 2 | |
| 6.4.13 | 24 / 2 | |
| 6.4.12 | 24 / 2 | |
| 6.4.10 | 24 / 2 | |
| 6.4.9 | 24 / 2 | |
| 6.4.8 | 24 / 2 | |
| 6.4.7 | 24 / 2 | |
| 6.4.5 | 24 / 2 | |
| 6.4.4 | 24 / 2 | |
| 6.4.3 | 24 / 2 | |
| 6.4.2 | 24 / 2 | |
| 6.4.1 | 24 / 2 | |
| 6.4.0 | 24 / 2 | |
| 6.3.13 | 24 / 2 | |
| 6.3.12 | 24 / 2 | |
| 6.3.11 | 24 / 2 | |
| 6.3.10 | 24 / 2 | |
| 6.3.9 | 24 / 2 | |
| 6.3.8 | 24 / 2 | |
| 6.3.7 | 24 / 2 | |
| 6.3.6 | 24 / 2 | |
| 6.3.5 | 24 / 2 | |
| 6.3.4 | 24 / 2 | |
| 6.3.3 | 24 / 2 | |
| 6.3.2 | 24 / 2 | |
| 6.3.1 | 24 / 2 |
v7.6.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.6.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.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.
v7.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.
v7.5.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.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.
v7.4.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.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
v7.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.
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.