@storybook/builder-webpack5
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@storybook/client-logger | AI (phantom-deps): Same-org dep used transitively; stable false positive. | ai | |
| phantom-deps | phantom-dep:@swc/core | AI (phantom-deps): Loaded by swc-loader at runtime; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): Type-only dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@storybook/channels | AI (phantom-deps): Same-org dep used transitively; stable false positive. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Used transitively via config/webpack setup; stable for this package. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Bundled build output inlining deps like pretty-hrtime; standard for this package. | ai | |
| provenance | publisher-changed | AI (provenance): jreinhold is a long-standing Storybook maintainer; manual publish is expected. | ai | |
| phantom-deps | phantom-dep:style-loader | AI (phantom-deps): style-loader is a declared runtime dep used in webpack config generation, not directly imported in JS — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:css-loader | AI (phantom-deps): css-loader is a declared runtime dep used in webpack config generation, not directly imported in JS — stable false positive for this package. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 10.4.6 | 15 / 7 | |
| 10.4.5 | 15 / 7 | |
| 10.4.4 | 15 / 7 | |
| 10.4.3 | 15 / 7 | |
| 10.4.2 | 15 / 7 | |
| 10.4.1 | 15 / 7 | |
| 10.4.0 | 15 / 7 | |
| 10.3.6 | 15 / 7 | |
| 10.3.5 | 15 / 7 | |
| 10.3.4 | 15 / 7 | |
| 10.3.3 | 15 / 7 | |
| 10.3.2 | 15 / 7 | |
| 10.3.1 | 15 / 7 | |
| 10.3.0 | 15 / 7 | |
| 10.2.19 | 15 / 7 | |
| 10.2.18 | 15 / 7 | |
| 10.2.17 | 15 / 7 | |
| 10.2.16 | 15 / 7 | |
| 10.2.15 | 15 / 7 | |
| 10.2.14 | 15 / 7 | |
| 10.2.13 | 15 / 7 | |
| 10.2.12 | 15 / 7 | |
| 10.2.11 | 15 / 7 | |
| 10.2.10 | 15 / 7 | |
| 10.2.9 | 15 / 7 | |
| 10.2.8 | 15 / 7 | |
| 10.2.7 | 15 / 7 | |
| 10.2.6 | 15 / 7 | |
| 10.2.5 | 15 / 7 | |
| 10.2.4 | 15 / 7 | |
| 10.2.3 | 15 / 7 | |
| 10.2.2 | 15 / 7 | |
| 10.2.1 | 15 / 7 | |
| 10.2.0 | 16 / 7 | |
| 10.1.11 | 16 / 7 | |
| 10.1.10 | 16 / 7 | |
| 10.1.9 | 16 / 7 | |
| 10.1.8 | 16 / 7 | |
| 10.1.7 | 16 / 7 | |
| 10.1.6 | 16 / 7 | |
| 10.1.5 | 16 / 7 | |
| 10.1.4 | 16 / 7 | |
| 10.1.3 | 16 / 7 | |
| 10.1.2 | 16 / 7 | |
| 10.1.1 | 16 / 7 | |
| 10.1.0 | 16 / 7 | |
| 10.0.8 | 15 / 7 | |
| 10.0.7 | 15 / 7 | |
| 10.0.6 | 15 / 7 | |
| 10.0.5 | 15 / 7 | |
| 10.0.4 | 15 / 7 | |
| 10.0.3 | 15 / 7 | |
| 10.0.2 | 15 / 7 | |
| 10.0.1 | 15 / 7 | |
| 10.0.0 | 15 / 7 | |
| 9.1.20 | 15 / 7 | |
| 9.1.19 | 15 / 7 | |
| 9.1.18 | 15 / 7 | |
| 9.1.17 | 15 / 7 | |
| 8.6.18 | 24 / 8 | |
| 8.6.17 | 24 / 8 | |
| 8.6.16 | 24 / 8 | |
| 8.6.15 | 24 / 8 | |
| 7.6.24 | 38 / 7 | |
| 7.6.23 | 38 / 7 | |
| 7.6.22 | 38 / 7 | |
| 7.6.21 | 38 / 7 |
v10.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.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.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.
v9.1.19
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.
v9.1.18
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.
v9.1.17
3 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.
v8.6.18
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.
v8.6.17
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.
v8.6.16
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.
v8.6.15
3 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.
v7.6.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.22
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.
v7.6.21
3 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.