@storybook/addon-interactions
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Storybook org migrated publishing from storybook-bot to GitHub Actions; stable org-level change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects org CI migration, not account takeover; consistent with storybook monorepo release cadence. | ai | |
| phantom-deps | phantom-dep:ts-dedent | AI (phantom-deps): ts-dedent is a declared runtime dep; phantom-dep heuristic false positive for this bundled package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 8.6.18 | 5 / 8 | |
| 8.6.17 | 5 / 8 | |
| 8.6.16 | 5 / 8 | |
| 8.6.15 | 5 / 8 | |
| 8.6.14 | 5 / 8 | |
| 8.6.13 | 5 / 8 | |
| 7.6.24 | 5 / 16 | |
| 7.6.23 | 5 / 16 | |
| 7.6.22 | 5 / 16 | |
| 7.6.21 | 5 / 16 |
v8.6.18
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. 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.6.17
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. 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.6.16
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.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.24
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. 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.23
2 findingsThis version was published by a different npm account than previous versions on 2026-02-18. 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.22
2 findingsThis version was published by a different npm account than previous versions on 2026-02-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.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.