@storybook/test
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/chai | AI (dependencies): @types/chai is a well-known DefinitelyTyped package with millions of downloads; no real risk for this package. | ai | |
| phantom-deps | phantom-dep:@types/chai | AI (phantom-deps): Type-only dependency loaded by convention; not directly imported in runtime code. Expected pattern for TypeScript packages. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Storybook is a large monorepo that publishes many packages simultaneously via CI. Rapid successive publishes are expected and normal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): shilman is a long-standing Storybook core maintainer; publisher rotations within the Storybook team are expected and not indicative of compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @storybook/global is a first-party Storybook org package; adding intra-org deps is routine for this monorepo. | ai | |
| phantom-deps | phantom-dep:@storybook/csf | AI (phantom-deps): Same-org scope phantom dep in a monorepo sub-package; @storybook/csf is a legitimate Storybook dependency used indirectly. | ai | |
| phantom-deps | phantom-dep:@storybook/preview-api | AI (phantom-deps): Same-org dependency within the Storybook monorepo; phantom-dep detection is a known false positive for intra-monorepo packages. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @storybook/test is the official Storybook testing utility, not a typosquat of jest. Scoped under the legitimate @storybook org with 764 versions and a trusted publisher. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): @storybook/test is the official Storybook testing utility, not a typosquat of next. Levenshtein match is algorithmic noise for this well-established scoped package. | ai | |
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): @storybook/test intentionally wraps @vitest/expect and @vitest/spy — similarity to vitest is by design, not impersonation. | ai | |
| phantom-deps | phantom-dep:chai | AI (phantom-deps): chai is a declared dependency explicitly listed in bundler.noExternal, meaning it is bundled into the dist output rather than directly imported at source level. | ai | |
| phantom-deps | phantom-dep:@storybook/core-events | AI (phantom-deps): Same-org dependency within the Storybook monorepo; phantom-dep detection is a known false positive for intra-monorepo packages. | ai | |
| dependencies | unvetted-dep:@storybook/global | AI (dependencies): @storybook/global is a first-party Storybook package from the same org/monorepo; not a third-party risk. Stable accept for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Empty description is a known pattern in some Storybook monorepo packages; all other metadata (repo, homepage, license, keywords) is present and correct. | ai |
Versions (showing 100 of 103)
| Version | Deps | Published |
|---|---|---|
| 8.6.18 | 7 / 5 | |
| 8.6.17 | 7 / 5 | |
| 8.6.16 | 7 / 5 | |
| 8.6.15 | 7 / 5 | |
| 8.6.14 | 7 / 5 | |
| 8.6.13 | 7 / 5 | |
| 8.6.12 | 7 / 5 | |
| 8.6.11 | 7 / 5 | |
| 8.6.10 | 7 / 5 | |
| 8.6.9 | 7 / 5 | |
| 8.6.8 | 7 / 5 | |
| 8.6.7 | 7 / 5 | |
| 8.6.6 | 7 / 5 | |
| 8.6.5 | 7 / 5 | |
| 8.6.4 | 7 / 5 | |
| 8.6.3 | 7 / 5 | |
| 8.6.2 | 7 / 5 | |
| 8.6.1 | 7 / 5 | |
| 8.6.0 | 7 / 5 | |
| 8.5.8 | 8 / 5 | |
| 8.5.7 | 8 / 5 | |
| 8.5.6 | 8 / 5 | |
| 8.5.5 | 8 / 5 | |
| 8.5.4 | 8 / 5 | |
| 8.5.3 | 8 / 5 | |
| 8.5.2 | 8 / 5 | |
| 8.5.1 | 8 / 5 | |
| 8.5.0 | 8 / 5 | |
| 8.4.7 | 8 / 5 | |
| 8.4.6 | 8 / 5 | |
| 8.4.5 | 8 / 5 | |
| 8.4.4 | 8 / 5 | |
| 8.4.3 | 8 / 5 | |
| 8.4.2 | 8 / 5 | |
| 8.4.1 | 8 / 5 | |
| 8.4.0 | 8 / 5 | |
| 8.3.7 | 9 / 5 | |
| 8.3.6 | 9 / 5 | |
| 8.3.5 | 9 / 5 | |
| 8.3.4 | 9 / 5 | |
| 8.3.3 | 9 / 5 | |
| 8.3.2 | 9 / 5 | |
| 8.3.1 | 9 / 5 | |
| 8.3.0 | 9 / 5 | |
| 8.2.10 | 8 / 5 | |
| 8.2.9 | 8 / 5 | |
| 8.2.8 | 8 / 5 | |
| 8.2.7 | 8 / 5 | |
| 8.2.6 | 8 / 5 | |
| 8.2.5 | 8 / 5 | |
| 8.2.4 | 8 / 5 | |
| 8.2.3 | 8 / 5 | |
| 8.2.2 | 8 / 5 | |
| 8.2.1 | 8 / 5 | |
| 8.2.0 | 8 / 5 | |
| 8.1.11 | 10 / 5 | |
| 8.1.10 | 10 / 5 | |
| 8.1.9 | 10 / 5 | |
| 8.1.8 | 10 / 5 | |
| 8.1.7 | 10 / 5 | |
| 8.1.6 | 10 / 5 | |
| 8.1.5 | 10 / 5 | |
| 8.1.4 | 10 / 5 | |
| 8.1.3 | 10 / 5 | |
| 8.1.2 | 10 / 5 | |
| 8.1.1 | 10 / 5 | |
| 8.1.0 | 10 / 5 | |
| 8.0.10 | 10 / 4 | |
| 8.0.9 | 10 / 4 | |
| 8.0.8 | 11 / 3 | |
| 8.0.7 | 11 / 3 | |
| 8.0.6 | 11 / 3 | |
| 8.0.5 | 11 / 3 | |
| 8.0.4 | 11 / 3 | |
| 8.0.3 | 11 / 3 | |
| 8.0.2 | 11 / 3 | |
| 8.0.1 | 11 / 3 | |
| 8.0.0 | 11 / 3 | |
| 7.6.24 | 12 / 3 | |
| 7.6.23 | 12 / 3 | |
| 7.6.22 | 12 / 3 | |
| 7.6.21 | 12 / 3 | |
| 7.6.20 | 12 / 3 | |
| 7.6.19 | 12 / 3 | |
| 7.6.18 | 12 / 3 | |
| 7.6.17 | 12 / 3 | |
| 7.6.16 | 12 / 3 | |
| 7.6.15 | 12 / 3 | |
| 7.6.14 | 12 / 3 | |
| 7.6.13 | 12 / 3 | |
| 7.6.12 | 12 / 3 | |
| 7.6.11 | 12 / 3 | |
| 7.6.10 | 12 / 3 | |
| 7.6.9 | 12 / 3 | |
| 7.6.8 | 12 / 3 | |
| 7.6.7 | 12 / 3 | |
| 7.6.6 | 12 / 3 | |
| 7.6.5 | 12 / 3 | |
| 7.6.4 | 12 / 3 | |
| 7.6.3 | 12 / 3 |
v8.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.7
2 findingsThis version was published by a different npm account than previous versions on 2024-12-05. 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.
v8.4.6
2 findingsThis version was published by a different npm account than previous versions on 2024-11-29. 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.
v8.4.5
2 findingsThis version was published by a different npm account than previous versions on 2024-11-20. 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.
v8.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
2 findingsThis version was published by a different npm account than previous versions on 2024-11-05. 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.
v8.4.1
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.7
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.6
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.5
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.4
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.9
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.8
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.7
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.6
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.5
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.3
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.11
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.10
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.9
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.8
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.7
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.6
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.5
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.4
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.10
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.9
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.3
2 findingsPackage name '@storybook/test' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
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. 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v7.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.