@heroui/autocomplete
An autocomplete combines a text input with a listbox, allowing users to filter a list of options to items matching a query.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@react-aria/visually-hidden | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@react-aria/focus | AI (phantom-deps): Referenced in config/type files; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@heroui/use-aria-button | AI (phantom-deps): Same-org monorepo sibling; stable false positive. | ai | |
| phantom-deps | phantom-dep:@react-aria/interactions | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@heroui/spinner | AI (phantom-deps): Same-org monorepo sibling; declared for transitive consumers, not a direct import. | ai | |
| dependencies | unvetted-dep:@heroui/scroll-shadow | AI (dependencies): Same @heroui org scope; consistent pattern across all heroui component packages. | ai | |
| provenance | no-provenance | AI (provenance): HeroUI monorepo does not publish with Sigstore provenance; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@heroui/aria-utils | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on indirect usage patterns common in @heroui packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.3.34 | 16 / 0 | |
| 2.3.33 | 16 / 0 | |
| 2.3.32 | 16 / 0 | |
| 2.3.31 | 16 / 0 | |
| 2.3.30 | 16 / 0 | |
| 2.3.29 | 16 / 0 | |
| 2.3.28 | 16 / 0 | |
| 2.3.27 | 16 / 0 | |
| 2.3.26 | 16 / 0 | |
| 2.3.25 | 16 / 0 | |
| 2.3.24 | 16 / 0 | |
| 2.3.23 | 17 / 0 | |
| 2.3.22 | 17 / 0 | |
| 2.3.21 | 22 / 0 | |
| 2.3.20 | 22 / 0 | |
| 2.3.11 | 22 / 0 |
v2.3.33
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.3.32
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.3.31
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.3.30
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.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.22
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.3.21
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.3.20
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.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.