@chakra-ui/tooltip
A React Component for rendering dynamically positioned Tooltips
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are official @chakra-ui/* monorepo packages, part of normal internal refactor. | ai | |
| provenance | missing-githead | AI (provenance): Consistent with monorepo CI publish pattern from trusted maintainer. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo lockstep releases; established publisher with clean history. | ai | |
| phantom-deps | phantom-dep:@chakra-ui/hooks | AI (phantom-deps): Sibling monorepo package, common false positive | ai | |
| phantom-deps | phantom-dep:@chakra-ui/utils | AI (phantom-deps): Sibling monorepo package, common false positive | ai | |
| phantom-deps | phantom-dep:@chakra-ui/popper | AI (phantom-deps): Sibling monorepo package, common false positive | ai | |
| phantom-deps | phantom-dep:@chakra-ui/portal | AI (phantom-deps): Sibling monorepo package, common false positive | ai | |
| phantom-deps | phantom-dep:@chakra-ui/react-utils | AI (phantom-deps): Sibling monorepo package, common false positive | ai | |
| phantom-deps | phantom-dep:@chakra-ui/visually-hidden | AI (phantom-deps): Sibling monorepo package, common false positive | ai | |
| dependencies | unvetted-dep:@chakra-ui/dom-utils | AI (dependencies): Internal Chakra UI monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@chakra-ui/portal | AI (dependencies): Internal Chakra UI monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-types | AI (dependencies): Internal Chakra UI monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@chakra-ui/shared-utils | AI (dependencies): Internal Chakra UI monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-disclosure | AI (dependencies): Internal Chakra UI monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-merge-refs | AI (dependencies): Internal Chakra UI monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@chakra-ui/react-use-event-listener | AI (dependencies): Internal Chakra UI monorepo sibling; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@chakra-ui/popper | AI (dependencies): Internal Chakra UI monorepo sibling; stable pattern across all versions. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 8 / 9 | |
| 2.3.0 | 8 / 9 | |
| 2.2.9 | 8 / 9 | |
| 2.2.8 | 7 / 9 | |
| 2.2.7 | 7 / 9 | |
| 2.2.6 | 7 / 9 | |
| 2.2.5 | 7 / 9 | |
| 2.2.4 | 7 / 9 | |
| 2.2.3 | 6 / 10 | |
| 2.2.2 | 6 / 10 | |
| 2.2.1 | 6 / 10 | |
| 2.2.0 | 6 / 10 | |
| 2.1.0 | 6 / 9 | |
| 2.0.10 | 6 / 8 | |
| 2.0.9 | 6 / 5 | |
| 2.0.8 | 6 / 5 | |
| 2.0.7 | 6 / 5 | |
| 2.0.6 | 6 / 5 | |
| 2.0.5 | 6 / 4 | |
| 2.0.4 | 6 / 4 | |
| 2.0.3 | 6 / 4 | |
| 2.0.2 | 6 / 4 | |
| 2.0.1 | 6 / 4 | |
| 2.0.0 | 6 / 4 |
v2.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: segunadebayo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.