@storybook/web-components-vite
Storybook for Web Components and Vite: 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:@storybook/core-server | AI (phantom-deps): Same-org dep used indirectly via bundled preset; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/node-logger | AI (phantom-deps): Same-org dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/web-components | AI (phantom-deps): Same-org dep used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:magic-string | AI (phantom-deps): Referenced in config/bundler context; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): jreinhold is a known Storybook core maintainer; publishing directly rather than via GitHub Actions is a legitimate workflow variation. | ai | |
| provenance | no-provenance | AI (provenance): Storybook publishes via GitHub Actions CI; provenance absence is consistent across the monorepo and not a risk indicator. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 10.4.2 | 2 / 2 | |
| 10.4.1 | 2 / 2 | |
| 10.4.0 | 2 / 2 | |
| 10.3.6 | 2 / 2 | |
| 10.3.5 | 2 / 2 | |
| 10.3.4 | 2 / 2 | |
| 10.3.3 | 2 / 2 | |
| 10.3.2 | 2 / 2 | |
| 10.3.1 | 2 / 2 | |
| 10.3.0 | 2 / 2 | |
| 10.2.19 | 2 / 2 | |
| 10.2.18 | 2 / 2 | |
| 10.2.17 | 2 / 2 | |
| 10.2.16 | 2 / 2 | |
| 10.2.15 | 2 / 2 | |
| 10.2.14 | 2 / 2 | |
| 10.2.13 | 2 / 2 | |
| 10.2.12 | 2 / 2 | |
| 10.2.11 | 2 / 2 | |
| 10.2.10 | 2 / 2 | |
| 10.2.9 | 2 / 2 | |
| 10.2.8 | 2 / 2 | |
| 10.2.7 | 2 / 2 | |
| 10.2.6 | 2 / 2 | |
| 10.2.5 | 2 / 2 | |
| 10.2.4 | 2 / 2 | |
| 10.2.3 | 2 / 2 | |
| 10.2.2 | 2 / 2 | |
| 10.2.1 | 2 / 2 | |
| 10.2.0 | 2 / 2 | |
| 10.1.11 | 2 / 2 | |
| 10.1.10 | 2 / 2 | |
| 10.1.9 | 2 / 2 | |
| 10.1.8 | 2 / 2 | |
| 10.1.7 | 2 / 2 | |
| 10.1.6 | 2 / 2 | |
| 10.1.5 | 2 / 2 | |
| 10.1.4 | 2 / 2 | |
| 10.1.3 | 2 / 2 | |
| 10.1.2 | 2 / 2 | |
| 10.1.1 | 2 / 2 | |
| 10.1.0 | 2 / 2 | |
| 10.0.8 | 2 / 2 | |
| 10.0.7 | 2 / 2 | |
| 10.0.6 | 2 / 2 | |
| 10.0.5 | 2 / 2 | |
| 10.0.4 | 2 / 2 | |
| 10.0.3 | 2 / 2 | |
| 10.0.2 | 2 / 2 | |
| 10.0.1 | 2 / 2 | |
| 10.0.0 | 2 / 2 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.