@storybook/cli
Storybook CLI: 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/run-YXTQBW3D.js | AI (source-diff): CLI tool legitimately uses network + child_process; bundled output, not malicious. | ai | |
| source-diff | obfuscated-file:dist/_node-chunks/run-YXTQBW3D.js | AI (source-diff): esbuild-bundled output with CJS compat banner; standard Storybook build artifact. | ai | |
| source-diff | obfuscated-file:dist/_node-chunks/run-CMSUW4EI.js | AI (source-diff): esbuild-bundled output for Storybook CLI; minified chunks are expected. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Normal churn for a large CLI tool rebundled with esbuild across versions. | ai | |
| source-diff | net-exec-file:dist/_node-chunks/run-CMSUW4EI.js | AI (source-diff): CLI tool legitimately uses network + exec (e.g. init, upgrade); bundled output. | ai | |
| source-diff | net-exec-file:dist/_node-chunks/run-7LEO2IWT.js | AI (source-diff): CLI tool legitimately uses network + exec; bundled output, not a dropper. | ai | |
| source-diff | obfuscated-file:dist/_node-chunks/run-7LEO2IWT.js | AI (source-diff): esbuild-bundled output with CJS compat banner; standard for Storybook's build pipeline. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo automated release; expected for @storybook packages. | ai | |
| phantom-deps | phantom-dep:@babel/preset-env | AI (phantom-deps): @babel/preset-env is a framework-scoped package loaded by convention in Storybook's build pipeline; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): @types/semver is a type declaration package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:jscodeshift | AI (phantom-deps): jscodeshift is a legitimate declared dependency used by convention in the CLI's codemod tooling, not a phantom dep. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @storybook/cli is a well-established scoped package with 3000+ days of history; Levenshtein match against 'joi' is a false positive with no plausible typosquat relationship. | ai | |
| source-diff | net-exec-file:dist/_node-chunks/run-UE2YPBJ7.js | AI (source-diff): Network + code execution is expected for a CLI tool that upgrades Storybook dependencies, fetches npm package data, and runs codemods. The sample shows legitimate Storybook CLI functionality. | ai | |
| source-diff | obfuscated-file:dist/_node-chunks/run-UE2YPBJ7.js | AI (source-diff): Storybook CLI ships esbuild-bundled dist chunks with long lines; this is standard build output, not obfuscation. The CJS compat banner and named Storybook function imports confirm legitimate bundled code. | ai |
Versions (showing 100 of 486)
| Version | Deps | Published |
|---|---|---|
| 10.4.1 | 7 / 15 | |
| 10.4.0 | 7 / 15 | |
| 10.3.6 | 7 / 14 | |
| 10.3.5 | 7 / 14 | |
| 10.3.4 | 7 / 14 | |
| 10.3.3 | 7 / 14 | |
| 10.3.2 | 7 / 14 | |
| 10.3.1 | 7 / 14 | |
| 10.3.0 | 7 / 14 | |
| 10.2.19 | 7 / 14 | |
| 10.2.18 | 7 / 14 | |
| 10.2.17 | 7 / 14 | |
| 10.2.16 | 7 / 14 | |
| 10.2.15 | 7 / 14 | |
| 10.2.14 | 7 / 14 | |
| 10.2.13 | 7 / 14 | |
| 10.2.12 | 7 / 14 | |
| 10.2.11 | 7 / 14 | |
| 10.2.10 | 7 / 14 | |
| 10.2.9 | 7 / 14 | |
| 10.2.8 | 7 / 14 | |
| 10.2.7 | 7 / 14 | |
| 10.2.6 | 7 / 14 | |
| 10.2.5 | 7 / 14 | |
| 10.2.4 | 7 / 14 | |
| 10.2.3 | 7 / 14 | |
| 10.2.2 | 7 / 14 | |
| 10.2.1 | 7 / 14 | |
| 10.2.0 | 7 / 14 | |
| 10.1.11 | 7 / 14 | |
| 10.1.10 | 7 / 14 | |
| 10.1.9 | 7 / 14 | |
| 10.1.8 | 7 / 14 | |
| 10.1.7 | 7 / 14 | |
| 10.1.6 | 7 / 14 | |
| 10.1.5 | 7 / 14 | |
| 10.1.4 | 7 / 14 | |
| 10.1.3 | 7 / 14 | |
| 10.1.2 | 7 / 14 | |
| 10.1.1 | 7 / 14 | |
| 10.1.0 | 7 / 14 | |
| 10.0.8 | 8 / 17 | |
| 10.0.7 | 8 / 17 | |
| 10.0.6 | 8 / 17 | |
| 10.0.5 | 8 / 17 | |
| 10.0.4 | 8 / 17 | |
| 10.0.3 | 8 / 17 | |
| 10.0.2 | 8 / 17 | |
| 10.0.1 | 8 / 17 | |
| 10.0.0 | 8 / 17 | |
| 9.1.20 | 8 / 17 | |
| 9.1.19 | 8 / 17 | |
| 9.1.18 | 8 / 17 | |
| 9.1.17 | 8 / 17 | |
| 9.1.16 | 8 / 17 | |
| 9.1.15 | 8 / 17 | |
| 9.1.14 | 8 / 17 | |
| 9.1.13 | 8 / 17 | |
| 9.1.12 | 8 / 17 | |
| 9.1.11 | 8 / 17 | |
| 9.1.10 | 8 / 17 | |
| 9.1.9 | 8 / 17 | |
| 9.1.8 | 8 / 17 | |
| 9.1.7 | 8 / 17 | |
| 9.1.6 | 8 / 17 | |
| 9.1.5 | 8 / 17 | |
| 9.1.4 | 8 / 17 | |
| 9.1.3 | 8 / 17 | |
| 9.1.2 | 8 / 17 | |
| 9.1.1 | 8 / 17 | |
| 9.1.0 | 8 / 17 | |
| 9.0.18 | 8 / 17 | |
| 9.0.17 | 8 / 17 | |
| 9.0.16 | 8 / 17 | |
| 9.0.15 | 8 / 17 | |
| 9.0.14 | 8 / 17 | |
| 9.0.13 | 18 / 8 | |
| 9.0.12 | 18 / 8 | |
| 9.0.11 | 18 / 7 | |
| 9.0.10 | 18 / 7 | |
| 9.0.9 | 18 / 7 | |
| 9.0.8 | 18 / 7 | |
| 9.0.6 | 18 / 7 | |
| 9.0.5 | 18 / 7 | |
| 9.0.4 | 18 / 7 | |
| 9.0.3 | 18 / 7 | |
| 9.0.2 | 18 / 7 | |
| 9.0.1 | 18 / 7 | |
| 9.0.0 | 18 / 7 | |
| 8.6.18 | 21 / 7 | |
| 8.6.17 | 21 / 7 | |
| 8.6.16 | 21 / 7 | |
| 8.6.15 | 21 / 7 | |
| 8.6.14 | 21 / 7 | |
| 8.6.13 | 21 / 7 | |
| 8.6.12 | 21 / 7 | |
| 8.6.11 | 21 / 7 | |
| 8.6.10 | 21 / 7 | |
| 8.6.9 | 21 / 7 | |
| 8.6.8 | 21 / 7 |
v10.4.1
3 findingsNewly 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.4.0
3 findingsNewly 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.6
3 findingsNewly 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.5
3 findingsNewly 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.
v10.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
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.
v9.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
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.
v8.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.