← Home

@storybook/react-fuzzy

npm Repository Homepage

React Fuzzy Component

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

hypnosphialexandrebodinshilmanaaronmcadammnmtanishusulproarunodamthuretndelangen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from ndelangen to hypnosphi reflects a legitimate Storybook org handoff in 2017. hypnosphi has 13,201 approved packages and 0 rejections — no compromise indicators. ai
maintainer-change maintainer-added AI (maintainer-change): hypnosphi is a well-established Storybook ecosystem contributor; maintainer addition is consistent with legitimate org-level transfer. ai

Versions (showing 3 of 3)

Version Deps Published
0.4.3 4 / 34
0.4.1 4 / 34
0.4.0 4 / 34

v0.4.3

2 findings
HIGH Publisher changed: ndelangen → hypnosphi (on 2017-10-22) provenance

This version was published by a different npm account than previous versions on 2017-10-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.