@tamagui/build
A small, opinionated build script for libraries that target both React Native and React web.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @tamagui package; Levenshtein match to uuid is a false positive for this well-known framework. | ai | |
| typosquat | typosquat.levenshtein:esbuild | AI (typosquat): Scoped @tamagui package; match to esbuild is incidental, not a squatting attempt. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): Build tooling; referenced in config/scripts, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:esbuild-register | AI (phantom-deps): Referenced in config files; stable false positive for this build tool. | ai | |
| phantom-deps | phantom-dep:esbuild-plugin-es5 | AI (phantom-deps): Referenced in config files; stable false positive for this build tool. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): Type-only dev dependency; framework-scoped, stable false positive. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 15 / 1 | |
| 2.0.0 | 15 / 1 | |
| 1.144.4 | 14 / 2 | |
| 1.144.3 | 14 / 2 | |
| 1.144.2 | 14 / 2 | |
| 1.144.1 | 14 / 2 | |
| 1.144.0 | 15 / 1 | |
| 1.143.1 | 14 / 1 | |
| 1.143.0 | 14 / 1 | |
| 1.142.0 | 14 / 1 | |
| 1.141.5 | 14 / 1 | |
| 1.141.4 | 14 / 1 | |
| 1.141.3 | 14 / 1 | |
| 1.141.2 | 14 / 1 | |
| 1.141.1 | 14 / 1 | |
| 1.141.0 | 14 / 1 | |
| 1.140.4 | 14 / 1 | |
| 1.140.3 | 14 / 1 | |
| 1.140.2 | 14 / 1 | |
| 1.140.1 | 14 / 1 | |
| 1.140.0 | 14 / 1 | |
| 1.139.4 | 14 / 1 | |
| 1.139.3 | 14 / 1 | |
| 1.139.2 | 14 / 1 | |
| 1.139.1 | 14 / 1 | |
| 1.139.0 | 14 / 1 | |
| 1.138.6 | 14 / 1 | |
| 1.138.5 | 14 / 1 | |
| 1.138.4 | 14 / 1 | |
| 1.138.3 | 14 / 1 | |
| 1.138.2 | 14 / 1 | |
| 1.138.1 | 14 / 1 | |
| 1.138.0 | 14 / 1 | |
| 1.137.3 | 14 / 1 | |
| 1.137.2 | 14 / 1 | |
| 1.137.1 | 14 / 1 | |
| 1.137.0 | 14 / 1 | |
| 1.136.9 | 14 / 1 | |
| 1.136.8 | 14 / 1 | |
| 1.136.7 | 14 / 1 | |
| 1.136.6 | 14 / 1 | |
| 1.136.4 | 14 / 1 | |
| 1.136.3 | 14 / 1 | |
| 1.136.2 | 14 / 1 | |
| 1.136.1 | 14 / 1 | |
| 1.136.0 | 14 / 1 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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.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.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. 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.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.3
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.140.0
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.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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.138.4
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.138.0
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.1
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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.136.3
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. 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.