← Home

@heroui/aria-utils

npm Repository Homepage

A package for managing @react-aria HeroUI utils.

16
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

juniorgarciadev

Keywords

aria-utils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 16 of 16)

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.8 8 / 0

v2.2.28

1 finding
LOW No provenance attestation provenance

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

v2.2.27

1 finding
LOW No provenance attestation provenance

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

v2.2.26

1 finding
LOW No provenance attestation provenance

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

v2.2.25

1 finding
LOW No provenance attestation provenance

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

v2.2.24

1 finding
LOW No provenance attestation provenance

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

v2.2.23

1 finding
LOW No provenance attestation provenance

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

v2.2.22

1 finding
LOW No provenance attestation provenance

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

v2.2.21

1 finding
LOW No provenance attestation provenance

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

v2.2.20

1 finding
LOW No provenance attestation provenance

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

v2.2.19

1 finding
LOW No provenance attestation provenance

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

v2.2.18

1 finding
LOW No provenance attestation provenance

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

v2.2.17

1 finding
LOW No provenance attestation provenance

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

v2.2.16

1 finding
LOW No provenance attestation provenance

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

v2.2.15

1 finding
LOW No provenance attestation provenance

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