@storybook/react
Storybook React renderer
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:util-deprecate | AI (phantom-deps): Utility referenced in config/build files but not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/escodegen | AI (phantom-deps): Type package for escodegen; loaded indirectly through build system; expected for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package loaded by convention in TypeScript/Storybook build pipeline; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/estree | AI (phantom-deps): Type package for AST handling; loaded indirectly through acorn/escodegen tooling; expected for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/preview-api | AI (phantom-deps): Legitimate monorepo dependency within @storybook scope; declared and used transitively in bundled output. | ai | |
| phantom-deps | phantom-dep:@storybook/theming | AI (phantom-deps): Legitimate monorepo dependency within @storybook scope; declared and used transitively in bundled output. | ai | |
| phantom-deps | phantom-dep:@storybook/components | AI (phantom-deps): Legitimate monorepo dependency within @storybook scope; declared and used transitively in bundled output. | ai | |
| phantom-deps | phantom-dep:@storybook/manager-api | AI (phantom-deps): Legitimate monorepo dependency within @storybook scope; declared and used transitively in bundled output. | ai | |
| dependencies | unvetted-dep:@storybook/global | AI (dependencies): @storybook/global is a first-party Storybook org package used as a utility across the Storybook ecosystem; unvetted status reflects review gap, not actual risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Storybook package published via GitHub Actions; lack of Sigstore attestation is a process gap, not a security signal for this well-known package. | ai |
Versions (showing 100 of 913)
| Version | Deps | Published |
|---|---|---|
| 8.6.7 | 6 / 20 | |
| 8.6.6 | 6 / 20 | |
| 8.6.5 | 6 / 20 | |
| 8.6.4 | 6 / 20 | |
| 8.6.3 | 6 / 20 | |
| 8.6.2 | 6 / 20 | |
| 8.6.1 | 6 / 20 | |
| 8.6.0 | 6 / 20 | |
| 8.5.8 | 6 / 20 | |
| 8.5.7 | 6 / 20 | |
| 8.5.6 | 6 / 20 | |
| 8.5.5 | 6 / 20 | |
| 8.5.4 | 6 / 20 | |
| 8.5.3 | 6 / 20 | |
| 8.5.2 | 6 / 20 | |
| 8.5.1 | 6 / 20 | |
| 8.5.0 | 6 / 20 | |
| 8.4.7 | 6 / 20 | |
| 8.4.6 | 6 / 20 | |
| 8.4.5 | 6 / 20 | |
| 8.4.4 | 6 / 20 | |
| 8.4.3 | 6 / 20 | |
| 8.4.2 | 6 / 20 | |
| 8.4.1 | 6 / 20 | |
| 8.4.0 | 6 / 20 | |
| 8.3.7 | 20 / 8 | |
| 8.3.6 | 20 / 8 | |
| 8.3.5 | 20 / 8 | |
| 8.3.4 | 20 / 8 | |
| 8.3.3 | 20 / 8 | |
| 8.3.2 | 20 / 8 | |
| 8.3.1 | 20 / 8 | |
| 8.3.0 | 20 / 8 | |
| 8.2.10 | 21 / 8 | |
| 8.2.9 | 21 / 8 | |
| 8.2.8 | 21 / 8 | |
| 8.2.7 | 21 / 8 | |
| 8.2.6 | 21 / 8 | |
| 8.2.5 | 21 / 8 | |
| 8.2.4 | 21 / 8 | |
| 8.2.3 | 17 / 8 | |
| 8.2.2 | 17 / 8 | |
| 8.2.1 | 17 / 8 | |
| 8.2.0 | 17 / 8 | |
| 8.1.11 | 21 / 7 | |
| 8.1.10 | 21 / 7 | |
| 8.1.9 | 21 / 7 | |
| 8.1.8 | 21 / 7 | |
| 8.1.7 | 21 / 7 | |
| 8.1.6 | 21 / 7 | |
| 8.1.5 | 21 / 7 | |
| 8.1.4 | 21 / 7 | |
| 8.1.3 | 21 / 7 | |
| 8.1.2 | 21 / 7 | |
| 8.1.1 | 21 / 7 | |
| 8.1.0 | 21 / 7 | |
| 8.0.10 | 21 / 7 | |
| 8.0.9 | 21 / 7 | |
| 8.0.8 | 21 / 7 | |
| 8.0.7 | 21 / 7 | |
| 8.0.6 | 21 / 7 | |
| 8.0.5 | 21 / 7 | |
| 8.0.4 | 21 / 7 | |
| 8.0.3 | 21 / 7 | |
| 8.0.2 | 21 / 7 | |
| 8.0.1 | 21 / 7 | |
| 8.0.0 | 21 / 7 | |
| 7.6.24 | 21 / 6 | |
| 7.6.23 | 21 / 6 | |
| 7.6.22 | 21 / 6 | |
| 7.6.21 | 21 / 6 | |
| 7.6.20 | 21 / 6 | |
| 7.6.19 | 21 / 6 | |
| 7.6.18 | 21 / 6 | |
| 7.6.17 | 21 / 6 | |
| 7.6.16 | 21 / 6 | |
| 7.6.15 | 21 / 6 | |
| 7.6.14 | 21 / 6 | |
| 7.6.13 | 21 / 6 | |
| 7.6.12 | 21 / 6 | |
| 7.6.11 | 21 / 6 | |
| 7.6.10 | 21 / 6 | |
| 7.6.9 | 21 / 6 | |
| 7.6.8 | 21 / 6 | |
| 7.6.7 | 21 / 6 | |
| 7.6.6 | 21 / 6 | |
| 7.6.5 | 21 / 6 | |
| 7.6.4 | 21 / 6 | |
| 7.6.3 | 21 / 6 | |
| 7.6.2 | 21 / 6 | |
| 7.6.1 | 21 / 6 | |
| 7.6.0 | 21 / 6 | |
| 7.5.3 | 21 / 5 | |
| 7.5.2 | 21 / 5 | |
| 7.5.1 | 21 / 5 | |
| 7.5.0 | 21 / 5 | |
| 7.4.6 | 21 / 5 | |
| 7.4.5 | 21 / 5 | |
| 7.4.4 | 21 / 5 | |
| 7.4.3 | 21 / 5 |
v8.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.