@storybook/preset-react-webpack
Storybook for React: Develop React Component in isolation with Hot Reloading
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): Type-only dependency used by bundled TypeScript; not directly imported at runtime. | ai | |
| provenance | publisher-changed | AI (provenance): storybook-bot is the documented Storybook CI release account; transition from GitHub Actions is expected automation pattern. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Legitimate dep used in build/preset tooling; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/react | AI (phantom-deps): Same-org peer/runtime dep; loaded by convention in Storybook preset architecture. | ai | |
| phantom-deps | phantom-dep:@babel/preset-flow | AI (phantom-deps): Babel preset loaded by name string at runtime, not via direct import; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only dep; not directly imported at runtime by design. | ai | |
| source-diff | obfuscated-file:dist/framework-preset-react.js | AI (source-diff): Standard esbuild-bundled CJS output; minified format is expected for all dist files in this package. | ai | |
| source-diff | obfuscated-file:dist/loaders/react-docgen-loader.mjs | AI (source-diff): Bundled/minified build artifact for a webpack loader; content is readable React docgen logic, not obfuscated malware. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): find-up is a well-known utility used directly in the docgen loader; benign addition. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 10.4.1 | 9 / 3 | |
| 10.4.0 | 9 / 3 | |
| 10.3.6 | 9 / 3 | |
| 10.3.5 | 9 / 3 | |
| 10.3.4 | 9 / 3 | |
| 10.3.3 | 9 / 3 | |
| 10.3.2 | 9 / 3 | |
| 10.3.1 | 9 / 3 | |
| 10.3.0 | 9 / 3 | |
| 10.2.19 | 9 / 3 | |
| 10.2.18 | 9 / 3 | |
| 10.2.17 | 9 / 3 | |
| 10.2.16 | 9 / 3 | |
| 10.2.15 | 9 / 3 | |
| 10.2.14 | 9 / 3 | |
| 10.2.13 | 9 / 3 | |
| 10.2.12 | 9 / 3 | |
| 10.2.11 | 9 / 3 | |
| 10.2.10 | 9 / 3 | |
| 10.2.9 | 9 / 3 | |
| 10.2.8 | 9 / 3 | |
| 10.2.7 | 9 / 3 | |
| 10.2.6 | 9 / 3 | |
| 10.2.5 | 9 / 3 | |
| 10.2.4 | 9 / 3 | |
| 10.2.3 | 9 / 3 | |
| 10.2.2 | 9 / 3 | |
| 10.2.1 | 9 / 3 | |
| 10.2.0 | 9 / 3 | |
| 10.1.11 | 9 / 3 | |
| 10.1.10 | 9 / 3 | |
| 10.1.9 | 9 / 3 | |
| 10.1.8 | 9 / 3 | |
| 10.1.7 | 9 / 3 | |
| 10.1.6 | 9 / 3 | |
| 10.1.5 | 9 / 3 | |
| 10.1.4 | 9 / 3 | |
| 10.1.3 | 9 / 3 | |
| 10.1.2 | 9 / 3 | |
| 10.1.1 | 9 / 3 | |
| 10.1.0 | 9 / 3 | |
| 10.0.8 | 9 / 3 | |
| 10.0.7 | 9 / 3 | |
| 10.0.6 | 9 / 3 | |
| 10.0.5 | 9 / 3 | |
| 10.0.4 | 9 / 3 | |
| 10.0.3 | 9 / 3 | |
| 10.0.2 | 9 / 3 | |
| 10.0.1 | 9 / 3 | |
| 10.0.0 | 9 / 3 | |
| 9.1.20 | 10 / 2 |
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.