@tamagui/select
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): Consistent with @tamagui monorepo sub-package conventions. | ai | |
| dependencies | unvetted-dep:@tamagui/list-item | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/use-previous | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/remove-scroll | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/create-context | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/animate-presence | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/use-controllable-state | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tamagui monorepo sub-packages legitimately lack standalone descriptions/repos; metadata is in the root package. | ai | |
| dependencies | unvetted-dep:@tamagui/text | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/adapt | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/sheet | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/portal | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/focusable | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/separator | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/dismissable | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/focus-scope | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@tamagui/use-debounce | AI (dependencies): Sibling tamagui monorepo package pinned at same version; standard monorepo release pattern. | ai | |
| phantom-deps | phantom-dep:@floating-ui/react-dom | AI (phantom-deps): Referenced in config/conditional exports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/remove-scroll | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package structure. | ai | |
| phantom-deps | phantom-dep:@tamagui/create-context | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package structure. | ai | |
| phantom-deps | phantom-dep:@floating-ui/react-native | AI (phantom-deps): Platform-specific dep; not imported on all platforms by design. | ai | |
| phantom-deps | phantom-dep:@tamagui/dismissable | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package structure. | ai | |
| phantom-deps | phantom-dep:@tamagui/use-event | AI (phantom-deps): Same-org monorepo dep; phantom detection is a false positive for this package structure. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 25 / 4 | |
| 2.0.0 | 25 / 4 | |
| 1.144.4 | 25 / 4 | |
| 1.142.0 | 25 / 4 | |
| 1.141.5 | 25 / 4 | |
| 1.141.2 | 25 / 4 | |
| 1.141.0 | 25 / 4 | |
| 1.140.2 | 25 / 4 | |
| 1.139.2 | 25 / 4 | |
| 1.139.0 | 25 / 4 | |
| 1.138.6 | 25 / 4 | |
| 1.138.5 | 25 / 4 | |
| 1.138.4 | 25 / 4 | |
| 1.138.3 | 25 / 4 | |
| 1.138.2 | 25 / 4 | |
| 1.138.1 | 25 / 4 | |
| 1.138.0 | 25 / 4 | |
| 1.137.3 | 25 / 4 | |
| 1.137.2 | 25 / 4 | |
| 1.137.1 | 25 / 4 | |
| 1.137.0 | 25 / 4 | |
| 1.136.9 | 25 / 4 | |
| 1.136.8 | 25 / 4 | |
| 1.136.7 | 25 / 4 | |
| 1.136.6 | 25 / 4 | |
| 1.136.5 | 25 / 4 | |
| 1.136.4 | 25 / 4 | |
| 1.136.3 | 25 / 4 | |
| 1.136.2 | 25 / 4 | |
| 1.136.1 | 25 / 4 | |
| 1.136.0 | 25 / 4 |
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.142.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.139.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.138.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.138.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. 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.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. 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.