← Home

@heroui/tooltip

npm Repository Homepage

A React Component for rendering dynamically positioned Tooltips

21
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

juniorgarciadev

Keywords

tooltip

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): HeroUI monorepo does not publish with Sigstore provenance; consistent across all package versions. ai
phantom-deps phantom-dep:@react-aria/interactions AI (phantom-deps): @react-aria/interactions is a direct dependency in package.json; phantom-dep is a false positive here. ai

Versions (showing 21 of 21)

Version Deps Published
2.2.29 12 / 0
2.2.28 12 / 0
2.2.27 12 / 0
2.2.26 12 / 0
2.2.25 12 / 0
2.2.24 12 / 0
2.2.23 12 / 0
2.2.22 12 / 0
2.2.21 12 / 0
2.2.20 12 / 0
2.2.19 12 / 0
2.2.18 12 / 0
2.2.17 13 / 0
2.2.16 13 / 0
2.2.15 13 / 0
2.2.14 13 / 0
2.2.13 13 / 0
2.2.12 13 / 0
2.2.11 13 / 0
2.2.8 13 / 0
2.2.7 13 / 0

v2.2.14

1 finding
INFO No provenance attestation provenance

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

v2.2.13

1 finding
INFO No provenance attestation provenance

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

v2.2.12

1 finding
INFO No provenance attestation provenance

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

v2.2.11

1 finding
INFO No provenance attestation provenance

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

v2.2.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.