@storybook/postinstall
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 migrated to GitHub Actions publishing; consistent across the org's packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects the package's stable utility role; resumed publishing aligns with Storybook 7.x maintenance cycle. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.6.24 | 0 / 4 | |
| 7.6.23 | 0 / 4 | |
| 7.6.22 | 0 / 4 | |
| 7.6.21 | 0 / 4 | |
| 7.6.20 | 0 / 4 | |
| 7.6.17 | 0 / 4 | |
| 6.5.10 | 1 / 3 |
v7.6.20
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 (valentinpalkovic) than the most recent previously approved version (shilman) on 2024-06-24, but valentinpalkovic 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.