@storybook/router
Core Storybook Router
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/index.js | AI (source-diff): Standard esbuild minified bundle output for @storybook/router; minification is expected for all dist/ files in this package. | ai | |
| source-diff | net-exec-file:dist/index.js | AI (source-diff): Network calls are browser history API (window.location); dynamic execution is lodash's Function('return this') global detection. No malicious payload. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): Standard esbuild minified ESM bundle; minification is expected for all dist/ files in this package. | ai | |
| source-diff | obfuscated-file:dist/utils.js | AI (source-diff): Standard esbuild minified bundle output; minification is expected for all dist/ files in this package. | ai | |
| source-diff | net-exec-file:dist/utils.js | AI (source-diff): Same pattern as index.js — lodash global detection and browser APIs, not malicious network+exec. | ai | |
| source-diff | net-exec-file:dist/chunk-4TLWAHSC.mjs | AI (source-diff): ESM chunk with qs/memoizerific imports and lodash internals; no malicious network or exec patterns. | ai |
Versions (showing 100 of 330)
| Version | Deps | Published |
|---|---|---|
| 7.6.2 | 3 / 8 | |
| 7.6.1 | 3 / 8 | |
| 7.6.0 | 3 / 8 | |
| 7.5.3 | 3 / 6 | |
| 7.5.2 | 3 / 6 | |
| 7.5.1 | 3 / 6 | |
| 7.5.0 | 3 / 6 | |
| 7.4.6 | 3 / 6 | |
| 7.4.5 | 3 / 6 | |
| 7.4.4 | 3 / 6 | |
| 7.4.3 | 3 / 6 | |
| 7.4.2 | 3 / 6 | |
| 7.4.1 | 3 / 6 | |
| 7.4.0 | 3 / 6 | |
| 7.3.2 | 3 / 6 | |
| 7.3.1 | 3 / 6 | |
| 7.3.0 | 3 / 6 | |
| 7.2.3 | 3 / 6 | |
| 7.2.2 | 3 / 6 | |
| 7.2.1 | 3 / 6 | |
| 7.2.0 | 3 / 6 | |
| 7.1.1 | 3 / 6 | |
| 7.1.0 | 3 / 6 | |
| 7.0.27 | 3 / 6 | |
| 7.0.26 | 3 / 6 | |
| 7.0.25 | 3 / 6 | |
| 7.0.24 | 3 / 6 | |
| 7.0.23 | 3 / 6 | |
| 7.0.22 | 3 / 6 | |
| 7.0.21 | 3 / 6 | |
| 7.0.20 | 3 / 6 | |
| 7.0.19 | 3 / 6 | |
| 7.0.18 | 3 / 6 | |
| 7.0.17 | 3 / 6 | |
| 7.0.16 | 3 / 6 | |
| 7.0.15 | 3 / 6 | |
| 7.0.14 | 3 / 6 | |
| 7.0.13 | 3 / 6 | |
| 7.0.12 | 3 / 6 | |
| 7.0.11 | 3 / 6 | |
| 7.0.10 | 3 / 6 | |
| 7.0.9 | 3 / 6 | |
| 7.0.8 | 3 / 6 | |
| 7.0.7 | 3 / 6 | |
| 7.0.6 | 3 / 6 | |
| 7.0.5 | 3 / 6 | |
| 7.0.4 | 3 / 6 | |
| 7.0.3 | 3 / 6 | |
| 7.0.2 | 3 / 6 | |
| 7.0.1 | 3 / 6 | |
| 7.0.0 | 3 / 6 | |
| 6.5.16 | 5 / 8 | |
| 6.5.15 | 5 / 8 | |
| 6.5.14 | 5 / 8 | |
| 6.5.13 | 5 / 8 | |
| 6.5.12 | 5 / 8 | |
| 6.5.11 | 5 / 8 | |
| 6.5.10 | 5 / 8 | |
| 6.5.9 | 5 / 8 | |
| 6.5.8 | 3 / 10 | |
| 6.5.7 | 3 / 10 | |
| 6.5.6 | 3 / 10 | |
| 6.5.5 | 3 / 10 | |
| 6.5.4 | 3 / 10 | |
| 6.5.3 | 3 / 10 | |
| 6.5.2 | 3 / 10 | |
| 6.5.0 | 3 / 10 | |
| 6.4.22 | 11 / 0 | |
| 6.4.21 | 11 / 0 | |
| 6.4.20 | 11 / 0 | |
| 6.4.19 | 11 / 0 | |
| 6.4.18 | 11 / 0 | |
| 6.4.17 | 11 / 0 | |
| 6.4.16 | 11 / 0 | |
| 6.4.15 | 11 / 0 | |
| 6.4.14 | 11 / 0 | |
| 6.4.13 | 11 / 0 | |
| 6.4.12 | 11 / 0 | |
| 6.4.10 | 11 / 0 | |
| 6.4.9 | 11 / 0 | |
| 6.4.8 | 11 / 0 | |
| 6.4.7 | 11 / 0 | |
| 6.4.5 | 11 / 0 | |
| 6.4.4 | 11 / 0 | |
| 6.4.3 | 11 / 0 | |
| 6.4.2 | 11 / 0 | |
| 6.4.1 | 11 / 0 | |
| 6.4.0 | 11 / 0 | |
| 6.3.13 | 10 / 0 | |
| 6.3.12 | 10 / 0 | |
| 6.3.11 | 10 / 0 | |
| 6.3.10 | 10 / 0 | |
| 6.3.9 | 10 / 0 | |
| 6.3.8 | 10 / 0 | |
| 6.3.7 | 10 / 0 | |
| 6.3.6 | 10 / 0 | |
| 6.3.5 | 10 / 0 | |
| 6.3.4 | 10 / 0 | |
| 6.3.3 | 10 / 0 | |
| 6.3.2 | 10 / 0 |
v7.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.