@heroui/dropdown
A dropdown displays a list of actions or options that a user can choose.
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): HeroUI monorepo packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.3.32 | 9 / 0 | |
| 2.3.31 | 9 / 0 | |
| 2.3.30 | 9 / 0 | |
| 2.3.29 | 9 / 0 | |
| 2.3.28 | 9 / 0 | |
| 2.3.27 | 9 / 0 | |
| 2.3.26 | 9 / 0 | |
| 2.3.25 | 9 / 0 | |
| 2.3.24 | 9 / 0 | |
| 2.3.23 | 9 / 0 | |
| 2.3.22 | 10 / 0 | |
| 2.3.21 | 10 / 0 | |
| 2.3.20 | 10 / 0 | |
| 2.3.19 | 10 / 0 | |
| 2.3.18 | 10 / 0 | |
| 2.3.17 | 10 / 0 | |
| 2.3.16 | 10 / 0 | |
| 2.3.15 | 10 / 0 | |
| 2.3.13 | 10 / 0 | |
| 2.3.10 | 10 / 0 | |
| 2.3.9 | 10 / 0 |
v2.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.13
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. Only ~12% of npm packages have provenance, so this is common but not ideal.