@storybook/vue3
Storybook Vue 3 renderer: Develop, document, and test UI components in isolation
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ts-dedent | AI (phantom-deps): Well-known utility used in config/template files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/manager-api | AI (phantom-deps): Same-org peer dep; phantom detection is a false positive for bundled storybook packages. | ai | |
| phantom-deps | phantom-dep:@storybook/preview-api | AI (phantom-deps): Same-org peer dep; phantom detection is a false positive for bundled storybook packages. | ai | |
| phantom-deps | phantom-dep:@vue/compiler-core | AI (phantom-deps): Framework-scoped dep loaded by convention in Vue3 renderer; stable false positive. | ai | |
| phantom-deps | phantom-dep:@storybook/theming | AI (phantom-deps): Same-org peer dep; phantom detection is a false positive for bundled storybook packages. | ai | |
| phantom-deps | phantom-dep:@storybook/components | AI (phantom-deps): Same-org peer dep; phantom detection is a false positive for bundled storybook packages. | ai | |
| provenance | publisher-changed | AI (provenance): storybook-bot is Storybook's documented CI publish account with 13k+ approved packages; not a suspicious takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All added deps are Storybook-org packages or well-known libs (lodash, @vue/compiler-core); consistent with backport release. | ai | |
| source-diff | obfuscated-file:dist/entry-preview-docs.mjs | AI (source-diff): Minified bundle output for a Storybook renderer; content is legitimate Vue source-decorator code. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 10.4.2 | 3 / 5 | |
| 10.4.1 | 3 / 5 | |
| 10.4.0 | 3 / 5 | |
| 10.3.6 | 3 / 5 | |
| 10.3.5 | 3 / 5 | |
| 10.3.4 | 3 / 5 | |
| 10.3.3 | 3 / 5 | |
| 10.3.2 | 3 / 5 | |
| 10.3.1 | 3 / 5 | |
| 10.3.0 | 3 / 5 | |
| 10.2.19 | 3 / 5 | |
| 10.2.18 | 3 / 5 | |
| 10.2.17 | 3 / 5 | |
| 10.2.16 | 3 / 5 | |
| 10.2.15 | 3 / 5 | |
| 10.2.14 | 3 / 5 | |
| 10.2.13 | 3 / 5 | |
| 10.2.12 | 3 / 5 | |
| 10.2.11 | 3 / 5 | |
| 10.2.10 | 3 / 5 | |
| 10.2.9 | 3 / 5 | |
| 10.2.8 | 3 / 5 | |
| 10.2.7 | 3 / 5 | |
| 10.2.6 | 3 / 5 | |
| 10.2.5 | 3 / 5 | |
| 10.2.4 | 3 / 5 | |
| 10.2.3 | 3 / 5 | |
| 10.2.2 | 3 / 5 | |
| 10.2.1 | 3 / 5 | |
| 10.2.0 | 3 / 5 | |
| 10.1.11 | 3 / 5 | |
| 10.1.10 | 3 / 5 | |
| 10.1.9 | 3 / 5 | |
| 10.1.8 | 3 / 5 | |
| 10.1.7 | 3 / 5 | |
| 10.1.6 | 3 / 5 | |
| 10.1.5 | 3 / 5 | |
| 10.1.4 | 3 / 5 | |
| 10.1.3 | 3 / 5 | |
| 10.1.2 | 3 / 5 | |
| 10.1.1 | 3 / 5 | |
| 10.1.0 | 3 / 5 | |
| 10.0.8 | 3 / 5 | |
| 10.0.7 | 3 / 5 | |
| 10.0.6 | 3 / 5 | |
| 10.0.5 | 3 / 5 | |
| 10.0.4 | 3 / 5 | |
| 10.0.3 | 3 / 5 | |
| 10.0.2 | 3 / 5 | |
| 10.0.1 | 3 / 5 | |
| 10.0.0 | 3 / 5 |
v10.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.