@tamagui/tooltip
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established monorepo component; missing description is stable pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is normal for this package family. | ai | |
| dependencies | unvetted-dep:@tamagui/popper | AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/popover | AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/floating | AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/polyfill-dev | AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/create-context | AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/use-controllable-state | AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. | ai | |
| phantom-deps | phantom-dep:@tamagui/compose-refs | AI (phantom-deps): Sibling org package; may be used transitively or in type declarations. | ai | |
| phantom-deps | phantom-dep:@tamagui/create-context | AI (phantom-deps): Sibling org package; may be used transitively or in type declarations. | ai | |
| dependencies | unvetted-dep:@tamagui/text | AI (dependencies): Sibling monorepo package pinned to same version; standard Tamagui release pattern. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 12 / 3 | |
| 2.0.0 | 12 / 3 | |
| 1.144.4 | 13 / 3 | |
| 1.144.3 | 13 / 3 | |
| 1.144.1 | 13 / 3 | |
| 1.144.0 | 13 / 3 | |
| 1.143.1 | 13 / 3 | |
| 1.142.0 | 13 / 3 | |
| 1.141.4 | 13 / 3 | |
| 1.141.2 | 13 / 3 | |
| 1.141.1 | 13 / 3 | |
| 1.140.2 | 13 / 3 | |
| 1.139.0 | 13 / 3 | |
| 1.138.2 | 13 / 3 | |
| 1.138.1 | 13 / 3 | |
| 1.136.9 | 13 / 3 | |
| 1.136.5 | 13 / 3 | |
| 1.136.3 | 13 / 3 | |
| 1.136.1 | 13 / 3 | |
| 1.136.0 | 13 / 3 |
v2.1.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.144.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.144.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.144.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.144.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.143.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.142.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.141.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.141.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.141.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.140.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.139.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.138.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.138.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.136.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.