expo-image-picker
Provides access to the system's UI for selecting images and videos from the phone's library or taking a photo with the camera.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Expo canary builds are published from a different CI environment that does not inject gitHead; this is consistent across canary releases from this publisher and not a meaningful risk signal. | ai | |
| dependencies | unvetted-dep:expo-permissions | AI (dependencies): expo-permissions is a sibling official Expo SDK package from the same expo/expo monorepo; its use here is expected and legitimate for permission handling in the image picker. | ai | |
| publish-pattern | suspicious-version-number | AI (publish-pattern): Expo uses date-stamped canary version strings (e.g., X.Y.Z-canary-YYYYMMDD-HASH) as a standard convention across all their packages. This pattern is not malicious. | ai | |
| phantom-deps | phantom-dep:expo-permissions | AI (phantom-deps): expo-permissions is referenced in Expo config/plugin files rather than direct JS imports; this is a standard pattern for Expo native modules and not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Established Expo SDK package from a known publisher; lack of provenance attestation is common and not a risk signal here. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer changes within the Expo organization are routine; no evidence of hostile takeover given the official repo URL and publisher track record. | ai | |
| provenance | publisher-changed | AI (provenance): brentvatne is a core Expo maintainer with a strong track record (91 approved packages); publisher rotation within the Expo org is expected and not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:expo-image-loader | AI (phantom-deps): expo-image-loader is a native module dependency referenced in config/plugin files rather than JS imports — expected pattern for Expo SDK packages. | ai | |
| dependencies | unvetted-dep:expo-image-loader | AI (dependencies): expo-image-loader is a first-party Expo monorepo package (github.com/expo/expo); unvetted status is a pipeline artifact, not a real risk. Stable for all versions of this package. | ai |
Versions (showing 34 of 134)
| Version | Deps | Published |
|---|---|---|
| 11.0.3 | 3 / 1 | |
| 11.0.2 | 3 / 1 | |
| 11.0.1 | 3 / 1 | |
| 11.0.0 | 3 / 1 | |
| 10.2.3 | 3 / 1 | |
| 10.2.2 | 4 / 1 | |
| 10.2.1 | 4 / 1 | |
| 10.2.0 | 4 / 1 | |
| 10.1.4 | 4 / 1 | |
| 10.1.3 | 4 / 1 | |
| 10.1.2 | 4 / 1 | |
| 10.1.1 | 4 / 1 | |
| 10.1.0 | 3 / 1 | |
| 10.0.0 | 3 / 1 | |
| 9.2.1 | 2 / 1 | |
| 9.2.0 | 2 / 1 | |
| 9.1.1 | 2 / 1 | |
| 9.1.0 | 2 / 1 | |
| 9.0.0 | 2 / 1 | |
| 8.4.0 | 2 / 1 | |
| 8.3.0 | 2 / 1 | |
| 8.2.0 | 2 / 1 | |
| 8.1.0 | 1 / 1 | |
| 8.0.2 | 1 / 1 | |
| 8.0.1 | 0 / 1 | |
| 8.0.0 | 0 / 1 | |
| 7.0.0 | 0 / 1 | |
| 6.0.0 | 0 / 1 | |
| 5.0.2 | 0 / 1 | |
| 5.0.1 | 0 / 1 | |
| 5.0.0 | 0 / 1 | |
| 4.0.0 | 0 / 1 | |
| 3.0.0 | 0 / 1 | |
| 1.0.0 | 0 / 1 |
v11.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.