@tamagui/alert-dialog
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/text | AI (dependencies): Same-org monorepo sibling dep; stable pattern across all @tamagui/* packages. | ai | |
| dependencies | unvetted-dep:@tamagui/dialog | AI (dependencies): Same-org monorepo sibling dep; stable pattern across all @tamagui/* packages. | ai | |
| dependencies | unvetted-dep:@tamagui/popper | AI (dependencies): Same-org monorepo sibling dep; stable pattern across all @tamagui/* packages. | ai | |
| dependencies | unvetted-dep:@tamagui/portal | AI (dependencies): Same-org monorepo sibling dep; stable pattern across all @tamagui/* packages. | ai | |
| dependencies | unvetted-dep:@tamagui/dismissable | AI (dependencies): Same-org monorepo sibling dep; stable pattern across all @tamagui/* packages. | ai | |
| dependencies | unvetted-dep:@tamagui/focus-scope | AI (dependencies): Same-org monorepo sibling dep; stable pattern across all @tamagui/* packages. | ai | |
| dependencies | unvetted-dep:@tamagui/animate-presence | AI (dependencies): Same-org monorepo sibling dep; stable pattern across all @tamagui/* packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo component package; missing metadata is a known pattern for @tamagui/* sub-packages. | ai | |
| phantom-deps | phantom-dep:@tamagui/create-context | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/text | AI (phantom-deps): Monorepo sub-package; sibling deps may be re-exported via @tamagui/dialog rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@tamagui/animate-presence | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/popper | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/portal | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/stacks | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/dismissable | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/focus-scope | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/polyfill-dev | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tamagui/remove-scroll | AI (phantom-deps): Same monorepo pattern; stable false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 15 / 3 | |
| 2.0.0 | 15 / 3 | |
| 1.144.1 | 16 / 3 | |
| 1.143.0 | 16 / 3 | |
| 1.142.0 | 16 / 3 | |
| 1.141.4 | 16 / 3 | |
| 1.141.1 | 16 / 3 | |
| 1.140.4 | 16 / 3 | |
| 1.140.0 | 16 / 3 | |
| 1.139.2 | 16 / 3 | |
| 1.138.6 | 16 / 3 | |
| 1.138.3 | 16 / 3 | |
| 1.138.1 | 16 / 3 | |
| 1.138.0 | 16 / 3 | |
| 1.137.2 | 16 / 3 | |
| 1.137.0 | 16 / 3 | |
| 1.136.7 | 16 / 3 | |
| 1.136.6 | 16 / 3 | |
| 1.136.4 | 16 / 3 | |
| 1.136.1 | 16 / 3 | |
| 1.136.0 | 16 / 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.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.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.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.0
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.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.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.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.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.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.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.