@storybook/core-server
Storybook framework-agnostic API
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 | obfuscated-file:dist/index.js | AI (source-diff): Standard esbuild bundle output for @storybook/core-server; samples show readable bundled third-party code, not obfuscation. This is the documented build pipeline for all Storybook packages. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Standard esbuild ESM bundle output; imports are clearly readable Storybook and third-party modules. Not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/multipart-parser-6L3XS67T.mjs | AI (source-diff): Minified multipart parser chunk from esbuild bundling; standard build artifact for this package. | ai | |
| source-diff | obfuscated-file:dist/presets/common-override-preset.js | AI (source-diff): Standard esbuild bundle output; samples show balanced-match, brace-expansion bundled code. Not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/presets/common-preset.js | AI (source-diff): Standard esbuild bundle output; samples show web-streams-polyfill bundled code. Not obfuscated. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/* packages are legitimately declared as runtime deps in Storybook packages for TypeScript type resolution; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): @types/* packages are legitimately declared as runtime deps in Storybook packages for TypeScript type resolution; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/detect-port | AI (phantom-deps): @types/* packages are legitimately declared as runtime deps in Storybook packages for TypeScript type resolution; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/pretty-hrtime | AI (phantom-deps): @types/* packages are legitimately declared as runtime deps in Storybook packages for TypeScript type resolution; stable false positive. | ai |
Versions (showing 51 of 226)
| Version | Deps | Published |
|---|---|---|
| 8.6.18 | 0 / 0 | |
| 8.6.17 | 0 / 0 | |
| 8.6.16 | 0 / 0 | |
| 8.6.15 | 0 / 0 | |
| 8.6.14 | 0 / 0 | |
| 8.6.13 | 0 / 0 | |
| 8.6.12 | 0 / 0 | |
| 8.6.11 | 0 / 0 | |
| 8.6.10 | 0 / 0 | |
| 8.6.9 | 0 / 0 | |
| 8.6.8 | 0 / 0 | |
| 8.6.7 | 0 / 0 | |
| 8.6.6 | 0 / 0 | |
| 8.6.5 | 0 / 0 | |
| 8.6.4 | 0 / 0 | |
| 8.6.3 | 0 / 0 | |
| 8.6.2 | 0 / 0 | |
| 8.6.1 | 0 / 0 | |
| 8.6.0 | 0 / 0 | |
| 8.5.8 | 0 / 0 | |
| 8.5.7 | 0 / 0 | |
| 8.5.6 | 0 / 0 | |
| 8.5.5 | 0 / 0 | |
| 8.5.4 | 0 / 0 | |
| 8.5.3 | 0 / 0 | |
| 8.5.2 | 0 / 0 | |
| 8.5.1 | 0 / 0 | |
| 8.5.0 | 0 / 0 | |
| 8.4.7 | 0 / 0 | |
| 8.4.6 | 0 / 0 | |
| 8.4.5 | 0 / 0 | |
| 8.4.4 | 0 / 0 | |
| 8.4.3 | 0 / 0 | |
| 8.4.2 | 0 / 0 | |
| 8.4.1 | 0 / 0 | |
| 8.4.0 | 0 / 0 | |
| 8.3.7 | 0 / 0 | |
| 8.3.6 | 0 / 0 | |
| 8.3.5 | 0 / 0 | |
| 8.3.4 | 0 / 0 | |
| 8.3.3 | 0 / 0 | |
| 8.3.2 | 0 / 0 | |
| 8.3.1 | 0 / 0 | |
| 8.3.0 | 0 / 0 | |
| 8.2.10 | 0 / 0 | |
| 8.2.9 | 0 / 0 | |
| 8.2.8 | 0 / 0 | |
| 8.2.7 | 0 / 0 | |
| 8.2.6 | 0 / 0 | |
| 8.2.5 | 0 / 0 | |
| 8.2.4 | 0 / 0 |
v8.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.5
2 findingsThis version was published by a different npm account than previous versions on 2024-11-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.