@newhighsco/storybook-preset
New High Score shareable Storybook preset
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:sass | AI (phantom-deps): Preset configures sass-loader; dependencies are referenced in config, not code. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Preset configures postcss-loader; dependencies are referenced in config, not code. | ai | |
| phantom-deps | phantom-dep:css-loader | AI (phantom-deps): Preset configures webpack loaders; dependencies are referenced in config, not code. | ai | |
| phantom-deps | phantom-dep:sass-loader | AI (phantom-deps): Preset configures webpack loaders; dependencies are referenced in config, not code. | ai | |
| phantom-deps | phantom-dep:style-loader | AI (phantom-deps): Preset configures webpack loaders; dependencies are referenced in config, not code. | ai | |
| phantom-deps | phantom-dep:postcss-loader | AI (phantom-deps): Preset configures webpack loaders; dependencies are referenced in config, not code. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-a11y | AI (phantom-deps): Preset includes Storybook addons via config; not directly imported in code. | ai | |
| phantom-deps | phantom-dep:@newhighsco/storybook-addon-svgr | AI (phantom-deps): Preset includes org-scoped addons via config; not directly imported in code. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-styling-webpack | AI (phantom-deps): Preset includes Storybook addons via config; not directly imported in code. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-webpack5-compiler-swc | AI (phantom-deps): Preset includes Storybook addons via config; not directly imported in code. | ai | |
| phantom-deps | phantom-dep:@newhighsco/storybook-addon-transpile-modules | AI (phantom-deps): Preset includes org-scoped addons via config; not directly imported in code. | ai |
Versions (showing 51 of 80)
| Version | Deps | Published |
|---|---|---|
| 10.2.51 | 14 / 0 | |
| 10.2.50 | 14 / 0 | |
| 10.2.49 | 14 / 0 | |
| 10.2.48 | 14 / 0 | |
| 10.2.47 | 14 / 0 | |
| 10.2.46 | 14 / 0 | |
| 10.2.45 | 14 / 0 | |
| 10.2.44 | 14 / 0 | |
| 10.2.43 | 14 / 0 | |
| 10.2.42 | 14 / 0 | |
| 10.2.41 | 14 / 0 | |
| 10.2.40 | 14 / 0 | |
| 10.2.39 | 14 / 0 | |
| 10.2.38 | 14 / 0 | |
| 10.2.37 | 14 / 0 | |
| 10.2.36 | 14 / 0 | |
| 10.2.35 | 14 / 0 | |
| 10.2.34 | 14 / 0 | |
| 10.2.33 | 14 / 0 | |
| 10.2.32 | 14 / 0 | |
| 10.2.31 | 14 / 0 | |
| 10.2.30 | 14 / 0 | |
| 10.2.29 | 14 / 0 | |
| 10.2.28 | 14 / 0 | |
| 10.2.27 | 14 / 0 | |
| 10.2.26 | 14 / 0 | |
| 10.2.25 | 14 / 0 | |
| 10.2.24 | 14 / 0 | |
| 10.2.23 | 14 / 0 | |
| 10.2.22 | 14 / 0 | |
| 10.2.21 | 14 / 0 | |
| 10.2.20 | 14 / 0 | |
| 10.2.19 | 14 / 0 | |
| 10.2.18 | 14 / 0 | |
| 10.2.17 | 14 / 0 | |
| 10.2.16 | 14 / 0 | |
| 10.2.15 | 14 / 0 | |
| 10.2.14 | 14 / 0 | |
| 10.2.13 | 14 / 0 | |
| 10.2.12 | 14 / 0 | |
| 10.2.11 | 14 / 0 | |
| 10.2.10 | 14 / 0 | |
| 10.2.9 | 14 / 0 | |
| 10.2.8 | 14 / 0 | |
| 10.2.7 | 14 / 0 | |
| 10.2.6 | 14 / 0 | |
| 10.2.5 | 14 / 0 | |
| 10.2.4 | 14 / 0 | |
| 10.2.3 | 14 / 0 | |
| 10.2.2 | 14 / 0 | |
| 10.2.1 | 14 / 0 |
v10.2.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.