@storybook/addon-storysource
View a story’s source code to see how it works and paste into your app
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/1c-ZL5ZTLKJ.js | AI (source-diff): Minified highlight.js language definition bundled for syntax highlighting. Content is recognizable grammar/keyword data, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/applescript-VW3BWF3R.js | AI (source-diff): Minified highlight.js language definition bundled for syntax highlighting. Content is recognizable grammar/keyword data, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/arcade-W3EOSWIA.js | AI (source-diff): Minified highlight.js language definition bundled for syntax highlighting. Content is recognizable grammar/keyword data, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/arduino-AQAPN62C.js | AI (source-diff): Minified highlight.js language definition bundled for syntax highlighting. Content is recognizable grammar/keyword data, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/armasm-A4MCERWV.js | AI (source-diff): Minified highlight.js language definition bundled for syntax highlighting. Content is recognizable grammar/keyword data, not malicious code. | ai | |
| source-diff | obfuscated-file:dist/autoit-TCITEG2N.js | AI (source-diff): Minified highlight.js language definition bundled for syntax highlighting. Content is recognizable grammar/keyword data, not malicious code. | ai | |
| provenance | no-provenance | AI (provenance): Official Storybook monorepo package published via GitHub Actions; no provenance attestation but publisher identity is well-established. | ai | |
| source-diff | obfuscated-file:dist/1c-JV6DWT74.js | AI (source-diff): Minified highlight.js language definition bundle (1c.js). Standard code-splitting output for syntax highlighter; no malicious content. | ai | |
| phantom-deps | phantom-dep:estraverse | AI (phantom-deps): estraverse is a declared runtime dependency used by @storybook/source-loader for AST traversal; phantom-dep detection is a false positive here. | ai | |
| source-diff | obfuscated-file:dist/applescript-TQ5KJUGN.js | AI (source-diff): Minified highlight.js language definition bundle (applescript.js). Standard code-splitting output for syntax highlighter; no malicious content. | ai | |
| source-diff | obfuscated-file:dist/arcade-LJZV75PA.js | AI (source-diff): Minified highlight.js language definition bundle (arcade.js). Standard code-splitting output for syntax highlighter; no malicious content. | ai | |
| source-diff | obfuscated-file:dist/arduino-N3NEMZMH.js | AI (source-diff): Minified highlight.js language definition bundle (arduino.js). Standard code-splitting output for syntax highlighter; no malicious content. | ai | |
| source-diff | obfuscated-file:dist/armasm-T6JWMN6W.js | AI (source-diff): Minified highlight.js language definition bundle (armasm.js). Standard code-splitting output for syntax highlighter; no malicious content. | ai | |
| source-diff | obfuscated-file:dist/autoit-2LQFRLGN.js | AI (source-diff): Minified highlight.js language definition bundle (autoit.js). Standard code-splitting output for syntax highlighter; no malicious content. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 751 new files are individual highlight.js language chunk files from code-splitting. Expected for a syntax-highlighting addon bundling all highlight.js languages. | ai |
Versions (showing 51 of 352)
| Version | Deps | Published |
|---|---|---|
| 8.6.18 | 3 / 6 | |
| 8.6.17 | 3 / 6 | |
| 8.6.16 | 3 / 6 | |
| 8.6.15 | 3 / 6 | |
| 8.6.14 | 3 / 6 | |
| 8.6.13 | 3 / 6 | |
| 8.6.12 | 3 / 6 | |
| 8.6.11 | 3 / 6 | |
| 8.6.10 | 3 / 6 | |
| 8.6.9 | 3 / 6 | |
| 8.6.8 | 3 / 6 | |
| 8.6.7 | 3 / 6 | |
| 8.6.6 | 3 / 6 | |
| 8.6.5 | 3 / 6 | |
| 8.6.4 | 3 / 6 | |
| 8.6.3 | 3 / 6 | |
| 8.6.2 | 3 / 6 | |
| 8.6.1 | 3 / 6 | |
| 8.6.0 | 3 / 6 | |
| 8.5.8 | 3 / 6 | |
| 8.5.7 | 3 / 6 | |
| 8.5.6 | 3 / 6 | |
| 8.5.5 | 3 / 6 | |
| 8.5.4 | 3 / 6 | |
| 8.5.3 | 3 / 6 | |
| 8.5.2 | 3 / 6 | |
| 8.5.1 | 3 / 6 | |
| 8.5.0 | 3 / 6 | |
| 8.4.7 | 3 / 6 | |
| 8.4.6 | 3 / 6 | |
| 8.4.5 | 3 / 6 | |
| 8.4.4 | 3 / 6 | |
| 8.4.3 | 3 / 6 | |
| 8.4.2 | 3 / 6 | |
| 8.4.1 | 3 / 6 | |
| 8.4.0 | 3 / 6 | |
| 8.3.7 | 3 / 6 | |
| 8.3.6 | 3 / 6 | |
| 8.3.5 | 3 / 6 | |
| 8.3.4 | 3 / 6 | |
| 8.3.3 | 3 / 6 | |
| 8.3.2 | 3 / 6 | |
| 8.3.1 | 3 / 6 | |
| 8.3.0 | 3 / 6 | |
| 8.2.10 | 3 / 6 | |
| 8.2.9 | 3 / 6 | |
| 8.2.8 | 3 / 6 | |
| 8.2.7 | 3 / 6 | |
| 8.2.6 | 3 / 6 | |
| 8.2.5 | 3 / 6 | |
| 8.2.4 | 3 / 6 |
v8.6.18
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v8.6.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.16
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v8.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.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.
v8.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.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.
v8.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.