← Home

@storybook/blocks

npm Repository Homepage

Storybook Doc Blocks

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ndelangenshilmantmeasdayghengeveldwinkervsbecksyannbfkylegachjreinholdkasperpeulenvalentinpalkovicdomyenstorybook-bot

Keywords

storybook

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/Color-6VNJS4EI.mjs AI (source-diff): Standard minified bundle output; sample shows legitimate React/styled-components color picker code with no malicious patterns. ai
phantom-deps phantom-dep:dequal AI (phantom-deps): Bundled dependency; phantom-dep heuristic fires on bundled packages that are not directly imported at source level. ai
phantom-deps phantom-dep:@types/lodash AI (phantom-deps): Type-only package; not imported at runtime, correctly flagged as phantom but benign. ai
phantom-deps phantom-dep:util-deprecate AI (phantom-deps): Transitive/bundled dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@storybook/manager-api AI (phantom-deps): Same-org package used via re-exports; phantom-dep heuristic false positive. ai
provenance publisher-changed AI (provenance): Storybook migrated publishing from storybook-bot to GitHub Actions CI; this is a legitimate org-level pipeline change. ai

Versions (showing 10 of 10)

Version Deps Published
8.6.18 2 / 13
8.6.17 2 / 13
8.6.16 2 / 13
8.6.15 2 / 13
8.6.14 2 / 13
8.6.13 2 / 13
7.6.24 23 / 2
7.6.23 23 / 2
7.6.22 23 / 2
7.6.21 23 / 2

v8.6.18

2 findings
HIGH Publisher changed: storybook-bot → GitHub Actions (on 2026-03-06) provenance

This version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.17

2 findings
HIGH Publisher changed: storybook-bot → GitHub Actions (on 2026-02-18) provenance

This version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.16

2 findings
HIGH Publisher changed: storybook-bot → GitHub Actions (on 2026-02-17) provenance

This version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.6.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.6.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.6.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.6.23

3 findings
HIGH Publisher changed: storybook-bot → GitHub Actions (on 2026-02-18) provenance

This version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/Color-6VNJS4EI.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.6.22

3 findings
HIGH Publisher changed: storybook-bot → GitHub Actions (on 2026-02-17) provenance

This version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: dist/Color-6VNJS4EI.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.6.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.