@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 919)
| Version | Deps | Published |
|---|---|---|
| 8.6.7 | 21 / 7 | |
| 8.6.6 | 21 / 7 | |
| 8.6.5 | 21 / 7 | |
| 8.6.4 | 21 / 7 | |
| 8.6.3 | 21 / 7 | |
| 8.6.2 | 21 / 7 | |
| 8.6.1 | 21 / 7 | |
| 8.6.0 | 21 / 7 | |
| 8.5.8 | 20 / 7 | |
| 8.5.7 | 20 / 7 | |
| 8.5.6 | 20 / 7 | |
| 8.5.5 | 20 / 7 | |
| 8.5.4 | 20 / 7 | |
| 8.5.3 | 20 / 7 | |
| 8.5.2 | 20 / 7 | |
| 8.5.1 | 20 / 7 | |
| 8.5.0 | 20 / 7 | |
| 8.4.7 | 20 / 7 | |
| 8.4.6 | 20 / 7 | |
| 8.4.5 | 20 / 7 | |
| 8.4.4 | 20 / 7 | |
| 8.4.3 | 20 / 7 | |
| 8.4.2 | 20 / 7 | |
| 8.4.1 | 20 / 7 | |
| 8.4.0 | 20 / 7 | |
| 8.3.7 | 22 / 6 | |
| 8.3.6 | 22 / 6 | |
| 8.3.5 | 22 / 6 | |
| 8.3.4 | 22 / 6 | |
| 8.3.3 | 22 / 6 | |
| 8.3.2 | 22 / 6 | |
| 8.3.1 | 22 / 6 | |
| 8.3.0 | 22 / 6 | |
| 8.2.10 | 1 / 0 | |
| 8.2.9 | 1 / 0 | |
| 8.2.8 | 1 / 0 | |
| 8.2.7 | 1 / 0 | |
| 8.2.6 | 1 / 0 | |
| 8.2.5 | 1 / 0 | |
| 8.2.4 | 1 / 0 | |
| 8.2.3 | 1 / 0 | |
| 8.2.2 | 1 / 0 | |
| 8.2.1 | 1 / 0 | |
| 8.2.0 | 1 / 0 | |
| 8.1.11 | 36 / 8 | |
| 8.1.10 | 36 / 8 | |
| 8.1.9 | 36 / 8 | |
| 8.1.8 | 36 / 8 | |
| 8.1.7 | 36 / 8 | |
| 8.1.6 | 36 / 8 | |
| 8.1.5 | 36 / 8 | |
| 8.1.4 | 36 / 8 | |
| 8.1.3 | 36 / 8 | |
| 8.1.2 | 36 / 8 | |
| 8.1.1 | 36 / 8 | |
| 8.1.0 | 36 / 8 | |
| 8.0.10 | 36 / 8 | |
| 8.0.9 | 36 / 8 | |
| 8.0.8 | 36 / 8 | |
| 8.0.7 | 36 / 8 | |
| 8.0.6 | 36 / 8 | |
| 8.0.5 | 36 / 8 | |
| 8.0.4 | 36 / 8 | |
| 8.0.3 | 36 / 8 | |
| 8.0.2 | 36 / 8 | |
| 8.0.1 | 36 / 8 | |
| 8.0.0 | 36 / 8 | |
| 7.6.24 | 40 / 9 | |
| 7.6.23 | 40 / 9 | |
| 7.6.22 | 40 / 9 | |
| 7.6.21 | 40 / 9 | |
| 7.6.20 | 40 / 9 | |
| 7.6.19 | 40 / 9 | |
| 7.6.18 | 40 / 9 | |
| 7.6.17 | 40 / 9 | |
| 7.6.16 | 40 / 9 | |
| 7.6.15 | 40 / 9 | |
| 7.6.14 | 40 / 9 | |
| 7.6.13 | 40 / 9 | |
| 7.6.12 | 40 / 9 | |
| 7.6.11 | 40 / 9 | |
| 7.6.10 | 40 / 9 | |
| 7.6.9 | 40 / 9 | |
| 7.6.8 | 41 / 9 | |
| 7.6.7 | 41 / 9 | |
| 7.6.6 | 41 / 10 | |
| 7.6.5 | 41 / 10 | |
| 7.6.4 | 41 / 10 | |
| 7.6.3 | 41 / 10 | |
| 7.6.2 | 41 / 10 | |
| 7.6.1 | 41 / 10 | |
| 7.6.0 | 41 / 10 | |
| 7.5.3 | 41 / 10 | |
| 7.5.2 | 41 / 10 | |
| 7.5.1 | 41 / 10 | |
| 7.5.0 | 41 / 10 | |
| 7.4.6 | 41 / 10 | |
| 7.4.5 | 41 / 10 | |
| 7.4.4 | 41 / 10 | |
| 7.4.3 | 41 / 10 |
v8.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.9
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.
v7.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.