@storybook/addon-links
Storybook Links: Link stories together to build demos and prototypes with your UI components
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@storybook/global | AI (dependencies): @storybook/global is a first-party package from the same Storybook org; it is a stable, intentional dependency across all Storybook packages. | ai |
Versions (showing 100 of 910)
| Version | Deps | Published |
|---|---|---|
| 8.6.12 | 2 / 1 | |
| 8.6.11 | 2 / 1 | |
| 8.6.10 | 2 / 1 | |
| 8.6.9 | 2 / 1 | |
| 8.6.8 | 2 / 1 | |
| 8.6.7 | 2 / 1 | |
| 8.6.6 | 2 / 1 | |
| 8.6.5 | 2 / 1 | |
| 8.6.4 | 2 / 1 | |
| 8.6.3 | 2 / 1 | |
| 8.6.2 | 2 / 1 | |
| 8.6.1 | 2 / 1 | |
| 8.6.0 | 2 / 1 | |
| 8.5.8 | 3 / 1 | |
| 8.5.7 | 3 / 1 | |
| 8.5.6 | 3 / 1 | |
| 8.5.5 | 3 / 1 | |
| 8.5.4 | 3 / 1 | |
| 8.5.3 | 3 / 1 | |
| 8.5.2 | 3 / 1 | |
| 8.5.1 | 3 / 1 | |
| 8.5.0 | 3 / 1 | |
| 8.4.7 | 3 / 1 | |
| 8.4.6 | 3 / 1 | |
| 8.4.5 | 3 / 1 | |
| 8.4.4 | 3 / 1 | |
| 8.4.3 | 3 / 1 | |
| 8.4.2 | 3 / 1 | |
| 8.4.1 | 3 / 1 | |
| 8.4.0 | 3 / 1 | |
| 8.3.7 | 3 / 2 | |
| 8.3.6 | 3 / 2 | |
| 8.3.5 | 3 / 2 | |
| 8.3.4 | 3 / 2 | |
| 8.3.3 | 3 / 2 | |
| 8.3.2 | 3 / 2 | |
| 8.3.1 | 3 / 2 | |
| 8.3.0 | 3 / 2 | |
| 8.2.10 | 3 / 2 | |
| 8.2.9 | 3 / 2 | |
| 8.2.8 | 3 / 2 | |
| 8.2.7 | 3 / 2 | |
| 8.2.6 | 3 / 2 | |
| 8.2.5 | 3 / 2 | |
| 8.2.4 | 3 / 2 | |
| 8.2.3 | 3 / 2 | |
| 8.2.2 | 3 / 2 | |
| 8.2.1 | 3 / 2 | |
| 8.2.0 | 3 / 2 | |
| 8.1.11 | 3 / 8 | |
| 8.1.10 | 3 / 8 | |
| 8.1.9 | 3 / 8 | |
| 8.1.8 | 3 / 8 | |
| 8.1.7 | 3 / 8 | |
| 8.1.6 | 3 / 8 | |
| 8.1.5 | 3 / 8 | |
| 8.1.4 | 3 / 8 | |
| 8.1.3 | 3 / 8 | |
| 8.1.2 | 3 / 8 | |
| 8.1.1 | 3 / 8 | |
| 8.1.0 | 3 / 8 | |
| 8.0.10 | 3 / 8 | |
| 8.0.9 | 3 / 8 | |
| 8.0.8 | 3 / 8 | |
| 8.0.7 | 3 / 8 | |
| 8.0.6 | 3 / 8 | |
| 8.0.5 | 3 / 8 | |
| 8.0.4 | 3 / 8 | |
| 8.0.3 | 3 / 8 | |
| 8.0.2 | 3 / 8 | |
| 8.0.1 | 3 / 8 | |
| 8.0.0 | 3 / 8 | |
| 7.6.24 | 3 / 8 | |
| 7.6.23 | 3 / 8 | |
| 7.6.22 | 3 / 8 | |
| 7.6.21 | 3 / 8 | |
| 7.6.20 | 3 / 8 | |
| 7.6.19 | 3 / 8 | |
| 7.6.18 | 3 / 8 | |
| 7.6.17 | 3 / 8 | |
| 7.6.16 | 3 / 8 | |
| 7.6.15 | 3 / 8 | |
| 7.6.14 | 3 / 8 | |
| 7.6.13 | 3 / 8 | |
| 7.6.12 | 3 / 8 | |
| 7.6.11 | 3 / 8 | |
| 7.6.10 | 3 / 8 | |
| 7.6.9 | 3 / 8 | |
| 7.6.8 | 3 / 8 | |
| 7.6.7 | 3 / 8 | |
| 7.6.6 | 3 / 8 | |
| 7.6.5 | 3 / 8 | |
| 7.6.4 | 3 / 8 | |
| 7.6.3 | 3 / 8 | |
| 7.6.2 | 3 / 8 | |
| 7.6.1 | 3 / 8 | |
| 7.6.0 | 3 / 8 | |
| 7.5.3 | 10 / 2 | |
| 7.5.2 | 10 / 2 | |
| 7.5.1 | 10 / 2 |
v8.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.