@storybook/csf
Component Story Format (CSF) utilities
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @storybook/csf is a legitimate, high-download Storybook utility package with no relation to 'qs'. The Levenshtein match is purely coincidental and this is a stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Build output from tsup with --minify flag; standard minified bundle for this package, not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Added maintainers are known Storybook team members; reflects org-wide maintainer management. | ai | |
| provenance | no-provenance | AI (provenance): Established package predates widespread provenance adoption; low-risk signal. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from shilman to storybook-bot is a documented organizational transition to bot-managed publishing for the Storybook project. storybook-bot has 12,933 approved packages and 0 rejections. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.1.13 | 1 / 21 | |
| 0.1.12 | 1 / 21 | |
| 0.1.11 | 1 / 21 | |
| 0.1.10 | 1 / 21 | |
| 0.1.9 | 1 / 21 | |
| 0.1.8 | 1 / 21 | |
| 0.1.7 | 1 / 21 | |
| 0.1.6 | 1 / 21 | |
| 0.1.5 | 1 / 21 | |
| 0.1.4 | 1 / 21 | |
| 0.1.3 | 1 / 21 | |
| 0.1.2 | 1 / 21 | |
| 0.1.1 | 1 / 21 | |
| 0.1.0 | 1 / 21 | |
| 0.0.1 | 1 / 14 |
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
2 findingsThis version was published by a different npm account than previous versions on 2024-11-29. 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.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.