@expo/ui
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 versioning is a known Expo monorepo convention; 141 versions in registry confirms this is an established package, not a throwaway. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @expo/ui is a scoped package under the official Expo org namespace; Levenshtein match to 'uuid' is a false positive with no plausible impersonation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @expo/ui is a scoped package under the official Expo org namespace; Levenshtein match to 'pg' is a false positive with no plausible impersonation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @expo/ui is a scoped package under the official Expo org namespace; Levenshtein match to 'qs' is a false positive with no plausible impersonation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @expo/ui is a scoped package under the official Expo org namespace; Levenshtein match to 'joi' is a false positive with no plausible impersonation. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @expo/ui is a scoped package under the official Expo org namespace; Levenshtein match to 'yup' is a false positive with no plausible impersonation. | ai | |
| provenance | publisher-changed | AI (provenance): brentvatne is a well-known Expo core team member (3942 days on npm, 7947 approved packages). Switch from expo-bot to named maintainer is a legitimate team practice, not a compromise signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is a native UI module (SwiftUI/Jetpack Compose); empty JS entry point and minimal README are expected for platform-native packages in the Expo ecosystem. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 56.0.15 | 2 / 9 | |
| 56.0.14 | 2 / 9 | |
| 56.0.13 | 2 / 9 | |
| 56.0.12 | 2 / 9 | |
| 56.0.11 | 2 / 9 | |
| 56.0.10 | 2 / 9 | |
| 56.0.9 | 2 / 9 | |
| 56.0.8 | 2 / 9 | |
| 56.0.7 | 2 / 9 | |
| 56.0.6 | 2 / 9 | |
| 56.0.5 | 2 / 9 | |
| 56.0.4 | 2 / 9 | |
| 56.0.3 | 2 / 9 | |
| 56.0.2 | 2 / 9 | |
| 56.0.1 | 2 / 8 | |
| 56.0.0 | 2 / 8 | |
| 55.0.17 | 1 / 2 | |
| 55.0.16 | 1 / 2 | |
| 55.0.15 | 1 / 2 | |
| 55.0.14 | 1 / 2 | |
| 55.0.13 | 1 / 2 | |
| 55.0.12 | 1 / 2 | |
| 55.0.11 | 1 / 2 | |
| 55.0.10 | 1 / 2 | |
| 55.0.9 | 1 / 2 | |
| 55.0.8 | 1 / 2 | |
| 55.0.7 | 1 / 2 | |
| 55.0.6 | 1 / 2 | |
| 55.0.5 | 1 / 2 | |
| 55.0.4 | 1 / 2 | |
| 55.0.3 | 1 / 2 | |
| 55.0.2 | 1 / 2 | |
| 55.0.1 | 1 / 2 | |
| 55.0.0 | 1 / 2 | |
| 0.0.2 | 0 / 2 | |
| 0.0.1 | 0 / 2 | |
| 0.0.0 | 0 / 2 |
v56.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alanhughes) than the most recent previously approved version (brentvatne) on 2026-05-23, but alanhughes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v56.0.12
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
v56.0.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-21. This could indicate a legitimate maintainer transition or an account compromise.
v56.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.
v56.0.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-14. This could indicate a legitimate maintainer transition or an account compromise.
v56.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.