@storybook/preact-webpack5
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Storybook org migrated publishing to GitHub Actions CI; applies across all @storybook/* packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects org-level CI migration, not account takeover; consistent across the storybook monorepo. | ai | |
| phantom-deps | phantom-dep:@storybook/preact | AI (phantom-deps): Same-org dep declared as runtime dependency; phantom-dep heuristic false positive for re-export packages. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 8.6.18 | 3 / 3 | |
| 8.6.17 | 3 / 3 | |
| 8.6.16 | 3 / 3 | |
| 8.6.15 | 3 / 3 | |
| 8.6.14 | 3 / 3 | |
| 8.6.13 | 3 / 3 | |
| 8.6.12 | 3 / 3 | |
| 8.6.11 | 3 / 3 | |
| 8.6.10 | 3 / 3 | |
| 8.6.9 | 3 / 3 | |
| 8.6.8 | 3 / 3 | |
| 8.6.7 | 3 / 3 | |
| 8.6.6 | 3 / 3 | |
| 8.6.5 | 3 / 3 | |
| 8.6.4 | 3 / 3 | |
| 8.6.3 | 3 / 3 | |
| 8.6.2 | 3 / 3 | |
| 8.6.1 | 3 / 3 | |
| 8.6.0 | 3 / 3 | |
| 8.5.8 | 3 / 3 | |
| 8.5.7 | 3 / 3 | |
| 8.5.6 | 3 / 3 | |
| 8.5.5 | 3 / 3 | |
| 8.5.4 | 3 / 3 | |
| 8.5.3 | 3 / 3 | |
| 8.5.2 | 3 / 3 | |
| 8.5.1 | 3 / 3 | |
| 8.5.0 | 3 / 3 | |
| 8.4.7 | 4 / 2 | |
| 8.4.6 | 4 / 2 | |
| 8.4.5 | 4 / 2 | |
| 8.4.4 | 4 / 2 | |
| 8.4.3 | 4 / 2 | |
| 8.4.2 | 4 / 2 | |
| 8.4.1 | 4 / 2 | |
| 8.4.0 | 4 / 2 | |
| 8.3.7 | 4 / 2 | |
| 8.3.6 | 4 / 2 | |
| 8.3.5 | 4 / 2 | |
| 8.3.4 | 4 / 2 | |
| 8.3.3 | 4 / 2 | |
| 8.3.2 | 4 / 2 | |
| 8.3.1 | 4 / 2 | |
| 8.3.0 | 4 / 2 | |
| 8.2.10 | 4 / 2 | |
| 8.2.9 | 4 / 2 | |
| 8.2.8 | 4 / 2 | |
| 8.2.7 | 4 / 2 | |
| 8.2.6 | 4 / 2 | |
| 8.2.5 | 4 / 2 | |
| 8.2.4 | 4 / 2 |
v8.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.5
2 findingsThis version was published by a different npm account (storybook-bot) than the most recent previously approved version (shilman) on 2024-11-20. It has since remained available on npm for 605 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (shilman) than the most recent previously approved version (kasperpeulen) on 2024-11-13, but shilman is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v8.4.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (shilman) than the most recent previously approved version (kasperpeulen) on 2024-11-05, but shilman is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kasperpeulen) than the most recent previously approved version (shilman) on 2024-11-04, but kasperpeulen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v8.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kasperpeulen) than the most recent previously approved version (shilman) on 2024-11-04, but kasperpeulen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v8.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.