tamagui
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tamagui/get-button-sized | AI (phantom-deps): First-party @tamagui scoped dep; likely re-exported or used indirectly. | ai | |
| phantom-deps | phantom-dep:@tamagui/get-font-sized | AI (phantom-deps): First-party @tamagui scoped dep; likely re-exported or used indirectly. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are first-party @tamagui/* scoped packages at matching semver; expected for a major version release. | ai | |
| phantom-deps | phantom-dep:@tamagui/focusable | AI (phantom-deps): First-party @tamagui scoped dep; likely re-exported or used indirectly via platform-specific entry points. | ai | |
| phantom-deps | phantom-dep:@tamagui/get-token | AI (phantom-deps): First-party @tamagui scoped dep; likely re-exported or used indirectly. | ai | |
| dependencies | unvetted-dep:@tamagui/adapt | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/group | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/label | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/sheet | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/avatar | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/button | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/dialog | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/portal | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/select | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/slider | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/switch | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/popover | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/tooltip | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/checkbox | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/progress | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/popper | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/card | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/form | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/tabs | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| dependencies | unvetted-dep:@tamagui/text | AI (dependencies): First-party @tamagui monorepo sub-package, same publisher and versioning. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tamagui is a well-known UI framework; sparse README/keywords are cosmetic, not indicative of spam. | ai | |
| phantom-deps | phantom-dep:@tamagui/fake-react-native | AI (phantom-deps): Platform-specific package for React Native; phantom-dep heuristic false positive for this monorepo package. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 63 / 4 | |
| 2.2.0 | 63 / 4 | |
| 2.1.0 | 63 / 4 | |
| 2.0.0 | 63 / 4 | |
| 1.144.4 | 53 / 4 | |
| 1.144.3 | 53 / 4 | |
| 1.144.2 | 53 / 4 | |
| 1.144.1 | 53 / 4 | |
| 1.144.0 | 53 / 4 | |
| 1.143.1 | 54 / 4 | |
| 1.143.0 | 54 / 4 | |
| 1.142.0 | 54 / 4 | |
| 1.141.5 | 53 / 4 | |
| 1.141.4 | 53 / 4 | |
| 1.141.3 | 53 / 4 | |
| 1.141.2 | 53 / 4 | |
| 1.141.1 | 53 / 4 | |
| 1.141.0 | 53 / 4 | |
| 1.140.4 | 53 / 4 | |
| 1.140.3 | 53 / 4 | |
| 1.140.2 | 53 / 4 | |
| 1.140.1 | 53 / 4 | |
| 1.140.0 | 53 / 4 | |
| 1.139.4 | 53 / 4 | |
| 1.139.3 | 53 / 4 | |
| 1.139.2 | 53 / 4 | |
| 1.139.1 | 53 / 4 | |
| 1.139.0 | 53 / 4 | |
| 1.138.6 | 53 / 4 | |
| 1.138.5 | 53 / 4 | |
| 1.138.4 | 53 / 4 | |
| 1.138.3 | 53 / 4 | |
| 1.138.2 | 53 / 4 | |
| 1.138.1 | 53 / 4 | |
| 1.138.0 | 53 / 4 | |
| 1.137.3 | 53 / 4 | |
| 1.137.2 | 53 / 4 | |
| 1.137.1 | 53 / 4 | |
| 1.137.0 | 53 / 4 | |
| 1.136.9 | 53 / 4 | |
| 1.136.8 | 53 / 4 | |
| 1.136.7 | 53 / 4 | |
| 1.136.6 | 53 / 4 | |
| 1.136.5 | 53 / 4 | |
| 1.136.4 | 53 / 4 | |
| 1.136.3 | 53 / 4 | |
| 1.136.2 | 53 / 4 | |
| 1.136.1 | 53 / 4 | |
| 1.136.0 | 53 / 4 | |
| 1.135.7 | 53 / 4 | |
| 1.135.6 | 53 / 4 | |
| 1.135.5 | 53 / 4 |
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.144.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.144.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.144.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.144.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.143.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.143.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.142.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.141.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.141.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.141.3
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.141.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.140.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.140.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.139.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.139.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.139.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.139.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.139.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.138.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.138.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.138.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.138.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.138.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.137.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.137.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.137.0
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.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.136.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.136.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.136.4
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.135.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.135.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.135.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.