storybook
Storybook: Develop, document, and test UI components in isolation
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/_node-chunks/builder-manager-EYIS5ER3.js | AI (source-diff): Storybook's esbuild build process bundles deps into node chunks with CJS compat banners; network+exec pattern is from bundled libs (ejs, babel), not malware. | ai | |
| source-diff | net-exec-file:dist/_node-chunks/chunk-GOY6UMCB.js | AI (source-diff): Same Storybook esbuild CJS compat banner pattern; bundled third-party libs, no malicious network/exec patterns. | ai | |
| source-diff | net-exec-file:dist/_node-chunks/chunk-JXXWBFBF.js | AI (source-diff): Same Storybook esbuild CJS compat banner pattern; bundled @babel/types and related libs, no malicious patterns. | ai | |
| source-diff | net-exec-file:dist/_node-chunks/mdx-N42X6CFJ-ODHTGV2Q.js | AI (source-diff): Bundled @storybook/docs-mdx with acorn parser; long lines are Unicode char code arrays from acorn, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/_node-chunks/mdx-N42X6CFJ-ODHTGV2Q.js | AI (source-diff): Long lines are acorn parser Unicode character code data arrays — a well-known pattern in JS parsers, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@vitest/spy | AI (phantom-deps): Testing framework package loaded by convention in Storybook's test utilities; not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@vitest/expect | AI (phantom-deps): Testing framework package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@testing-library/jest-dom | AI (phantom-deps): Testing library loaded by convention in Storybook test setup; stable false positive. | ai | |
| phantom-deps | phantom-dep:@testing-library/user-event | AI (phantom-deps): Testing library loaded by convention in Storybook test setup; stable false positive. | ai |
Versions (showing 51 of 237)
| Version | Deps | Published |
|---|---|---|
| 10.3.5 | 13 / 131 | |
| 10.3.4 | 13 / 131 | |
| 10.3.3 | 12 / 131 | |
| 10.3.2 | 12 / 131 | |
| 10.3.1 | 12 / 131 | |
| 10.3.0 | 12 / 131 | |
| 10.2.19 | 12 / 130 | |
| 10.2.18 | 12 / 130 | |
| 10.2.17 | 12 / 130 | |
| 10.2.16 | 12 / 130 | |
| 10.2.15 | 12 / 129 | |
| 10.2.14 | 12 / 129 | |
| 10.2.13 | 12 / 129 | |
| 10.2.12 | 12 / 129 | |
| 10.2.11 | 12 / 129 | |
| 10.2.10 | 12 / 129 | |
| 9.1.20 | 12 / 129 | |
| 9.1.19 | 12 / 128 | |
| 8.6.18 | 1 / 1 | |
| 8.6.17 | 1 / 1 | |
| 8.0.8 | 1 / 0 | |
| 8.0.7 | 1 / 0 | |
| 8.0.6 | 1 / 0 | |
| 8.0.5 | 1 / 0 | |
| 8.0.4 | 1 / 0 | |
| 8.0.3 | 1 / 0 | |
| 8.0.2 | 1 / 0 | |
| 8.0.1 | 1 / 0 | |
| 8.0.0 | 1 / 0 | |
| 7.6.24 | 1 / 0 | |
| 7.6.23 | 1 / 0 | |
| 7.6.22 | 1 / 0 | |
| 7.6.21 | 1 / 0 | |
| 7.6.17 | 1 / 0 | |
| 7.6.16 | 1 / 0 | |
| 7.6.15 | 1 / 0 | |
| 7.6.14 | 1 / 0 | |
| 7.6.13 | 1 / 0 | |
| 7.6.12 | 1 / 0 | |
| 7.6.11 | 1 / 0 | |
| 7.6.10 | 1 / 0 | |
| 7.6.9 | 1 / 0 | |
| 7.6.8 | 1 / 0 | |
| 7.6.7 | 1 / 0 | |
| 7.6.6 | 1 / 0 | |
| 7.6.5 | 1 / 0 | |
| 7.6.4 | 1 / 0 | |
| 7.6.3 | 1 / 0 | |
| 7.6.2 | 1 / 0 | |
| 7.6.1 | 1 / 0 | |
| 7.6.0 | 1 / 0 |
v10.3.5
6 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.