@heroui/scroll-shadow
A component that applies top and bottom shadows when content overflows on scroll.
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 | no-provenance | AI (provenance): Absence of Sigstore provenance is common and not a risk signal for this established HeroUI component. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.3.19 | 3 / 0 | |
| 2.3.18 | 3 / 0 | |
| 2.3.17 | 3 / 0 | |
| 2.3.16 | 3 / 0 | |
| 2.3.15 | 3 / 0 | |
| 2.3.14 | 3 / 0 | |
| 2.3.13 | 3 / 0 | |
| 2.3.12 | 3 / 0 | |
| 2.3.11 | 3 / 0 | |
| 2.3.10 | 3 / 0 | |
| 2.3.9 | 3 / 0 | |
| 2.3.7 | 3 / 0 | |
| 2.3.6 | 3 / 0 | |
| 2.3.5 | 3 / 0 |
v2.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.