@storybook/react-komposer
Generic way to compose data containers for React.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package is 3081 days old under the @storybook namespace; missing gitHead is a minor provenance gap with no other risk signals and no material changes from prior version. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from hypnosphi to shilman reflects a legitimate Storybook org transition; shilman is a core Storybook maintainer with a strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (christianalfoni, pksunkara, tmeasday) are known Storybook contributors; consistent with org-level maintainer consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers reflect the same org transition; no evidence of hostile takeover given publisher's strong track record. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2018, predating Sigstore/npm provenance attestation; not a meaningful risk signal for this era. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Low-severity cosmetic issues (off-topic README, no keywords); no malicious indicators. Package is a legitimate Storybook utility. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.5 | 5 / 19 | |
| 2.0.4 | 5 / 19 | |
| 2.0.3 | 5 / 19 | |
| 2.0.2 | 5 / 19 | |
| 2.0.1 | 5 / 19 |
v2.0.5
2 findingsThis version was published by a different npm account than previous versions on 2018-10-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: hypnosphi.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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.
v2.0.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.