@storybook/svelte
Storybook Svelte 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:@storybook/theming | AI (phantom-deps): Same-org monorepo dep. | ai | |
| phantom-deps | phantom-dep:@storybook/components | AI (phantom-deps): Same-org monorepo dep. | ai | |
| phantom-deps | phantom-dep:@storybook/manager-api | AI (phantom-deps): Same-org monorepo dep. | ai | |
| phantom-deps | phantom-dep:@storybook/preview-api | AI (phantom-deps): Same-org monorepo dep. | ai | |
| phantom-deps | phantom-dep:sveltedoc-parser | AI (phantom-deps): Referenced in config, used at build/prep time. | ai | |
| phantom-deps | phantom-dep:ts-dedent | AI (phantom-deps): Referenced in config files, long-standing dep. | ai | |
| phantom-deps | phantom-dep:@storybook/csf | AI (phantom-deps): Same-org monorepo dep, config-only reference is normal. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 10.5.5 | 2 / 7 | |
| 10.5.4 | 2 / 7 | |
| 10.5.3 | 2 / 7 | |
| 10.5.2 | 2 / 7 | |
| 10.5.1 | 2 / 7 | |
| 10.5.0 | 2 / 7 | |
| 10.4.6 | 2 / 7 | |
| 10.4.5 | 2 / 7 | |
| 10.4.4 | 2 / 7 | |
| 10.4.3 | 2 / 7 | |
| 10.4.2 | 2 / 7 | |
| 10.4.1 | 2 / 7 | |
| 10.4.0 | 2 / 7 | |
| 10.3.6 | 2 / 7 | |
| 10.3.5 | 2 / 7 | |
| 10.3.4 | 2 / 7 | |
| 10.3.3 | 2 / 7 | |
| 10.3.2 | 2 / 7 | |
| 10.3.1 | 2 / 7 | |
| 10.3.0 | 2 / 7 | |
| 10.2.19 | 2 / 7 | |
| 10.2.18 | 2 / 7 | |
| 10.2.17 | 2 / 7 | |
| 10.2.16 | 2 / 7 | |
| 10.2.15 | 2 / 7 | |
| 10.2.14 | 2 / 7 | |
| 10.2.13 | 2 / 7 | |
| 10.2.12 | 2 / 7 | |
| 10.2.11 | 2 / 7 | |
| 10.2.10 | 2 / 7 | |
| 10.2.9 | 2 / 7 | |
| 10.2.8 | 2 / 7 | |
| 10.2.7 | 2 / 7 | |
| 10.2.6 | 2 / 7 | |
| 10.2.5 | 2 / 7 | |
| 10.2.4 | 2 / 7 | |
| 10.2.3 | 2 / 7 | |
| 10.2.2 | 2 / 7 | |
| 10.2.1 | 2 / 7 | |
| 10.2.0 | 2 / 7 | |
| 10.1.11 | 2 / 7 | |
| 10.1.10 | 2 / 7 | |
| 10.1.9 | 2 / 7 | |
| 10.1.8 | 2 / 7 | |
| 10.1.7 | 2 / 7 | |
| 10.1.6 | 2 / 7 | |
| 10.1.5 | 2 / 7 | |
| 10.1.4 | 2 / 7 | |
| 10.1.3 | 2 / 7 | |
| 10.1.2 | 2 / 7 | |
| 10.1.1 | 2 / 7 | |
| 10.1.0 | 2 / 7 | |
| 10.0.8 | 2 / 7 | |
| 10.0.7 | 2 / 7 | |
| 10.0.6 | 2 / 7 | |
| 10.0.5 | 2 / 7 | |
| 10.0.4 | 2 / 7 | |
| 10.0.3 | 2 / 7 | |
| 10.0.2 | 2 / 7 | |
| 10.0.1 | 2 / 7 | |
| 10.0.0 | 2 / 7 | |
| 9.1.20 | 2 / 8 | |
| 9.1.19 | 2 / 8 | |
| 9.1.18 | 2 / 8 | |
| 9.1.17 | 2 / 8 | |
| 8.6.18 | 9 / 7 | |
| 8.6.17 | 9 / 7 | |
| 8.6.16 | 9 / 7 | |
| 8.6.15 | 9 / 7 | |
| 7.6.24 | 10 / 4 | |
| 7.6.23 | 10 / 4 | |
| 7.6.22 | 10 / 4 | |
| 7.6.21 | 10 / 4 |
v10.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.1.17
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jreinhold) than the most recent previously approved version (GitHub Actions) on 2025-12-17, but jreinhold is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (storybook-bot) than the most recent previously approved version (GitHub Actions) on 2025-12-17, but storybook-bot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (storybook-bot) than the most recent previously approved version (GitHub Actions) on 2025-12-17, but storybook-bot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.