@tamagui/sheet
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tamagui/adapt | AI (dependencies): Same-org sibling package in Tamagui monorepo; consistently co-versioned. | ai | |
| dependencies | unvetted-dep:@tamagui/animate-presence | AI (dependencies): Same-org sibling package in Tamagui monorepo; consistently co-versioned. | ai | |
| dependencies | unvetted-dep:@tamagui/portal | AI (dependencies): Same-org sibling package in Tamagui monorepo; consistently co-versioned. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all Tamagui sub-packages; not a risk signal for this org. | ai | |
| phantom-deps | phantom-dep:@tamagui/use-keyboard-visible | AI (phantom-deps): Tamagui monorepo sibling dep; may be used indirectly or conditionally in native builds. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Tamagui monorepo packages consistently lack standalone metadata; not indicative of spam. | ai | |
| phantom-deps | phantom-dep:@tamagui/animations-react-native | AI (phantom-deps): Tamagui monorepo sibling dep; conditionally used in react-native export path. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 18 / 4 | |
| 2.0.0 | 18 / 4 | |
| 1.144.3 | 17 / 3 | |
| 1.144.1 | 17 / 3 | |
| 1.143.0 | 17 / 3 | |
| 1.141.4 | 17 / 3 | |
| 1.141.1 | 17 / 3 | |
| 1.141.0 | 17 / 3 | |
| 1.140.4 | 17 / 3 | |
| 1.140.2 | 17 / 3 | |
| 1.140.1 | 17 / 3 | |
| 1.139.4 | 17 / 3 | |
| 1.139.3 | 17 / 3 | |
| 1.139.2 | 17 / 3 | |
| 1.139.0 | 17 / 3 | |
| 1.138.3 | 17 / 3 | |
| 1.138.1 | 17 / 3 | |
| 1.137.3 | 17 / 3 | |
| 1.137.2 | 17 / 3 | |
| 1.137.0 | 17 / 3 | |
| 1.136.9 | 17 / 3 | |
| 1.136.8 | 17 / 3 | |
| 1.136.4 | 17 / 3 | |
| 1.136.2 | 17 / 3 | |
| 1.136.0 | 17 / 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.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.143.0
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.1
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.4
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.140.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.139.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.136.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.