@canonical/storybook-config
Canonical's standard Storybook configuration factory
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@canonical/ds-assets | AI (phantom-deps): Config package references same-org deps in config files, not direct imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-a11y | AI (phantom-deps): Storybook addons referenced in config files, not imported directly; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-docs | AI (phantom-deps): Storybook addons referenced in config files, not imported directly; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@canonical/styles-debug | AI (phantom-deps): Same-org dep referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-vitest | AI (phantom-deps): Storybook addons referenced in config files; expected pattern. | ai | |
| phantom-deps | phantom-dep:@chromatic-com/storybook | AI (phantom-deps): Storybook addon referenced in config files; expected pattern. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-svelte-csf | AI (phantom-deps): Storybook addon referenced in config files; expected pattern. | ai | |
| phantom-deps | phantom-dep:@canonical/storybook-addon-utils | AI (phantom-deps): Same-org dep referenced in config files; stable false positive. | ai | |
| phantom-deps | phantom-dep:@canonical/storybook-addon-shell-theme | AI (phantom-deps): Same-org dep referenced in config files; stable false positive. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.27.0 | 12 / 8 | |
| 0.26.0 | 12 / 8 | |
| 0.25.0 | 12 / 8 | |
| 0.24.0 | 12 / 8 | |
| 0.23.0 | 12 / 8 | |
| 0.22.0 | 12 / 8 | |
| 0.21.0 | 12 / 8 | |
| 0.20.0 | 13 / 8 | |
| 0.17.1 | 13 / 8 | |
| 0.17.0 | 13 / 8 | |
| 0.16.0 | 13 / 8 | |
| 0.15.1 | 12 / 8 | |
| 0.15.0 | 12 / 8 | |
| 0.14.0 | 12 / 8 | |
| 0.13.0 | 12 / 8 | |
| 0.12.0 | 9 / 4 | |
| 0.11.0 | 8 / 4 | |
| 0.10.0 | 8 / 4 | |
| 0.9.0 | 7 / 4 |
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.