@heroui/aria-utils
A package for managing @react-aria HeroUI utils.
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 org consistently publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@heroui/shared-utils | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@heroui/react-rsc-utils | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@react-stately/overlays | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.2.29 | 5 / 0 | |
| 2.2.28 | 5 / 0 | |
| 2.2.27 | 5 / 0 | |
| 2.2.26 | 5 / 0 | |
| 2.2.25 | 5 / 0 | |
| 2.2.24 | 5 / 0 | |
| 2.2.23 | 5 / 0 | |
| 2.2.22 | 5 / 0 | |
| 2.2.21 | 5 / 0 | |
| 2.2.20 | 5 / 0 | |
| 2.2.19 | 5 / 0 | |
| 2.2.18 | 5 / 0 | |
| 2.2.17 | 8 / 0 | |
| 2.2.16 | 8 / 0 | |
| 2.2.15 | 8 / 0 | |
| 2.2.14 | 8 / 0 | |
| 2.2.13 | 8 / 0 | |
| 2.2.12 | 8 / 0 | |
| 2.2.11 | 8 / 0 | |
| 2.2.9 | 8 / 0 | |
| 2.2.8 | 8 / 0 | |
| 2.2.7 | 8 / 0 |
v2.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.