@storybook/api
Storybook Manager API (facade)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): @storybook/api is a core Storybook package, not a typosquat of hapi. The scoped name match is a false positive from Levenshtein distance on the full scoped package name. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @storybook/api is a legitimate Storybook core package; no relation to pg. False positive from string distance matching. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @storybook/api is a legitimate Storybook core package; no relation to joi. False positive from string distance matching. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @storybook/api is a legitimate Storybook core package; no relation to ajv. False positive from string distance matching. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): prop-types is a legitimate declared dependency for this React-based Storybook package; not directly imported in analyzed files but used by convention. | ai | |
| phantom-deps | phantom-dep:@types/reach__router | AI (phantom-deps): @types/reach__router is a type definition package loaded by convention for @reach/router; phantom-dep finding is expected and benign. | ai |
Versions (showing 100 of 224)
| Version | Deps | Published |
|---|---|---|
| 6.4.10 | 17 / 6 | |
| 6.4.9 | 17 / 6 | |
| 6.4.8 | 17 / 6 | |
| 6.4.7 | 17 / 6 | |
| 6.4.5 | 17 / 6 | |
| 6.4.4 | 17 / 6 | |
| 6.4.3 | 17 / 6 | |
| 6.4.2 | 17 / 6 | |
| 6.4.1 | 17 / 6 | |
| 6.4.0 | 17 / 6 | |
| 6.3.13 | 20 / 4 | |
| 6.3.12 | 20 / 4 | |
| 6.3.11 | 20 / 4 | |
| 6.3.10 | 20 / 4 | |
| 6.3.9 | 20 / 4 | |
| 6.3.8 | 20 / 4 | |
| 6.3.7 | 20 / 4 | |
| 6.3.6 | 20 / 4 | |
| 6.3.5 | 20 / 4 | |
| 6.3.4 | 20 / 4 | |
| 6.3.3 | 20 / 4 | |
| 6.3.2 | 20 / 4 | |
| 6.3.1 | 20 / 4 | |
| 6.3.0 | 20 / 4 | |
| 6.2.9 | 20 / 4 | |
| 6.2.8 | 20 / 4 | |
| 6.2.7 | 20 / 4 | |
| 6.2.6 | 20 / 4 | |
| 6.2.5 | 20 / 4 | |
| 6.2.4 | 20 / 4 | |
| 6.2.3 | 20 / 4 | |
| 6.2.2 | 20 / 4 | |
| 6.2.1 | 20 / 4 | |
| 6.2.0 | 20 / 4 | |
| 6.1.21 | 19 / 4 | |
| 6.1.20 | 19 / 4 | |
| 6.1.19 | 19 / 4 | |
| 6.1.18 | 19 / 4 | |
| 6.1.17 | 19 / 4 | |
| 6.1.16 | 19 / 4 | |
| 6.1.15 | 19 / 4 | |
| 6.1.14 | 19 / 4 | |
| 6.1.12 | 19 / 4 | |
| 6.1.11 | 19 / 4 | |
| 6.1.10 | 19 / 4 | |
| 6.1.9 | 19 / 4 | |
| 6.1.8 | 19 / 4 | |
| 6.1.7 | 19 / 4 | |
| 6.1.6 | 19 / 4 | |
| 6.1.5 | 19 / 4 | |
| 6.1.4 | 19 / 4 | |
| 6.1.3 | 19 / 4 | |
| 6.1.2 | 19 / 4 | |
| 6.1.1 | 19 / 4 | |
| 6.1.0 | 19 / 4 | |
| 6.0.28 | 20 / 4 | |
| 6.0.27 | 20 / 4 | |
| 6.0.26 | 20 / 4 | |
| 6.0.25 | 20 / 4 | |
| 6.0.24 | 20 / 4 | |
| 6.0.23 | 20 / 4 | |
| 6.0.22 | 20 / 4 | |
| 6.0.21 | 20 / 4 | |
| 6.0.20 | 20 / 4 | |
| 6.0.19 | 20 / 4 | |
| 6.0.18 | 20 / 4 | |
| 6.0.17 | 20 / 4 | |
| 6.0.16 | 20 / 4 | |
| 6.0.15 | 20 / 4 | |
| 6.0.14 | 20 / 4 | |
| 6.0.13 | 20 / 4 | |
| 6.0.12 | 20 / 4 | |
| 6.0.11 | 20 / 4 | |
| 6.0.10 | 20 / 4 | |
| 6.0.9 | 20 / 4 | |
| 6.0.7 | 20 / 4 | |
| 6.0.6 | 20 / 4 | |
| 6.0.5 | 20 / 4 | |
| 6.0.4 | 20 / 4 | |
| 6.0.3 | 20 / 4 | |
| 6.0.2 | 20 / 4 | |
| 6.0.1 | 20 / 4 | |
| 6.0.0 | 20 / 4 | |
| 5.3.22 | 20 / 2 | |
| 5.3.21 | 20 / 2 | |
| 5.3.20 | 20 / 2 | |
| 5.3.19 | 20 / 2 | |
| 5.3.18 | 20 / 2 | |
| 5.3.17 | 20 / 2 | |
| 5.3.15 | 20 / 2 | |
| 5.3.14 | 20 / 2 | |
| 5.3.13 | 20 / 2 | |
| 5.3.12 | 20 / 2 | |
| 5.3.11 | 20 / 2 | |
| 5.3.10 | 20 / 2 | |
| 5.3.9 | 20 / 2 | |
| 5.3.8 | 20 / 2 | |
| 5.3.7 | 20 / 2 | |
| 5.3.6 | 20 / 2 | |
| 5.3.5 | 20 / 2 |
v6.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.21
2 findingsPackage name '@storybook/api' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.