@storybook/addon-svelte-csf
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from storybook-bot to GitHub Actions is a CI/CD migration within the official storybookjs org, confirmed by SLSA provenance attestation. | ai | |
| dependencies | unvetted-dep:svelte-ast-print | AI (dependencies): svelte-ast-print is a legitimate Svelte AST utility; its use is appropriate for this Svelte CSF addon. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 5.1.2 | 7 / 40 | |
| 5.1.1 | 7 / 39 | |
| 5.1.0 | 7 / 39 | |
| 5.0.12 | 7 / 39 | |
| 5.0.11 | 7 / 39 | |
| 5.0.10 | 7 / 38 | |
| 5.0.9 | 7 / 38 | |
| 5.0.8 | 7 / 38 | |
| 5.0.7 | 7 / 38 | |
| 5.0.6 | 7 / 38 | |
| 5.0.5 | 7 / 38 | |
| 5.0.4 | 7 / 38 | |
| 5.0.3 | 7 / 38 | |
| 5.0.2 | 7 / 39 | |
| 5.0.1 | 7 / 42 | |
| 5.0.0 | 7 / 42 |
v5.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.10
2 findingsThis version was published by a different npm account than previous versions on 2025-10-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.