@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 234)
| Version | Deps | Published |
|---|---|---|
| 7.6.24 | 2 / 0 | |
| 7.6.23 | 2 / 0 | |
| 7.6.22 | 2 / 0 | |
| 7.6.21 | 2 / 0 | |
| 7.6.20 | 2 / 0 | |
| 7.6.19 | 2 / 0 | |
| 7.6.18 | 2 / 0 | |
| 7.6.17 | 2 / 0 | |
| 7.6.16 | 2 / 0 | |
| 7.6.15 | 2 / 0 | |
| 7.6.14 | 2 / 0 | |
| 7.6.13 | 2 / 0 | |
| 7.6.12 | 2 / 0 | |
| 7.6.11 | 2 / 0 | |
| 7.6.10 | 2 / 0 | |
| 7.6.9 | 2 / 0 | |
| 7.6.8 | 2 / 0 | |
| 7.6.7 | 2 / 0 | |
| 7.6.6 | 2 / 0 | |
| 7.6.5 | 2 / 0 | |
| 7.6.4 | 2 / 0 | |
| 7.6.3 | 2 / 0 | |
| 7.6.2 | 2 / 0 | |
| 7.6.1 | 2 / 0 | |
| 7.6.0 | 2 / 0 | |
| 7.5.3 | 2 / 0 | |
| 7.5.2 | 2 / 0 | |
| 7.5.1 | 2 / 0 | |
| 7.5.0 | 2 / 0 | |
| 7.4.6 | 2 / 0 | |
| 7.4.5 | 2 / 0 | |
| 7.4.4 | 2 / 0 | |
| 7.4.3 | 2 / 0 | |
| 7.4.2 | 2 / 0 | |
| 7.4.1 | 2 / 0 | |
| 7.4.0 | 2 / 0 | |
| 7.3.2 | 2 / 0 | |
| 7.3.1 | 2 / 0 | |
| 7.3.0 | 2 / 0 | |
| 7.2.3 | 2 / 0 | |
| 7.2.2 | 2 / 0 | |
| 7.2.1 | 2 / 0 | |
| 7.2.0 | 2 / 0 | |
| 7.1.1 | 2 / 0 | |
| 7.1.0 | 2 / 0 | |
| 7.0.27 | 2 / 0 | |
| 7.0.26 | 2 / 0 | |
| 7.0.25 | 2 / 0 | |
| 7.0.24 | 2 / 0 | |
| 7.0.23 | 2 / 0 | |
| 7.0.22 | 2 / 0 | |
| 7.0.21 | 2 / 0 | |
| 7.0.20 | 2 / 0 | |
| 7.0.19 | 2 / 0 | |
| 7.0.18 | 2 / 0 | |
| 7.0.17 | 2 / 0 | |
| 7.0.16 | 2 / 0 | |
| 7.0.15 | 2 / 0 | |
| 7.0.14 | 2 / 0 | |
| 7.0.13 | 2 / 0 | |
| 7.0.12 | 2 / 0 | |
| 7.0.11 | 2 / 0 | |
| 7.0.10 | 2 / 0 | |
| 7.0.9 | 2 / 0 | |
| 7.0.8 | 2 / 0 | |
| 7.0.7 | 2 / 0 | |
| 7.0.6 | 2 / 0 | |
| 7.0.5 | 2 / 0 | |
| 7.0.4 | 2 / 0 | |
| 7.0.3 | 2 / 0 | |
| 7.0.2 | 2 / 0 | |
| 7.0.1 | 2 / 0 | |
| 7.0.0 | 2 / 0 | |
| 6.5.16 | 17 / 6 | |
| 6.5.15 | 17 / 6 | |
| 6.5.14 | 17 / 6 | |
| 6.5.13 | 17 / 6 | |
| 6.5.12 | 17 / 6 | |
| 6.5.11 | 17 / 6 | |
| 6.5.10 | 17 / 6 | |
| 6.5.9 | 17 / 6 | |
| 6.5.8 | 17 / 6 | |
| 6.5.7 | 17 / 6 | |
| 6.5.6 | 17 / 6 | |
| 6.5.5 | 17 / 6 | |
| 6.5.4 | 17 / 6 | |
| 6.5.3 | 17 / 6 | |
| 6.5.2 | 17 / 6 | |
| 6.5.0 | 17 / 6 | |
| 6.4.22 | 17 / 6 | |
| 6.4.21 | 17 / 6 | |
| 6.4.20 | 17 / 6 | |
| 6.4.19 | 17 / 6 | |
| 6.4.18 | 17 / 6 | |
| 6.4.17 | 17 / 6 | |
| 6.4.16 | 17 / 6 | |
| 6.4.15 | 17 / 6 | |
| 6.4.14 | 17 / 6 | |
| 6.4.13 | 17 / 6 | |
| 6.4.12 | 17 / 6 |
v7.6.24
1 findingPackage 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.21
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.20
2 findingsThis version was published by a different npm account than previous versions on 2024-06-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.18
2 findingsThis version was published by a different npm account than previous versions on 2024-04-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.