expo-document-picker
Provides access to the system's UI for selecting documents from the available providers on the user's device.
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 | publisher-changed | AI (provenance): brentvatne is a known Expo core maintainer; publisher rotation within the Expo org is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal Expo team roster changes; kadikraman departure is a known org change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Expo monorepo packages publish on SDK release cadence; gaps between major versions are normal. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 56.0.4 | 0 / 3 | |
| 56.0.3 | 0 / 3 | |
| 56.0.2 | 0 / 3 | |
| 56.0.1 | 0 / 3 | |
| 56.0.0 | 0 / 2 | |
| 55.0.13 | 0 / 1 | |
| 55.0.12 | 0 / 1 | |
| 55.0.11 | 0 / 1 | |
| 55.0.10 | 0 / 1 | |
| 55.0.9 | 0 / 1 | |
| 55.0.8 | 0 / 1 | |
| 55.0.7 | 0 / 1 | |
| 55.0.6 | 0 / 1 | |
| 55.0.5 | 0 / 1 | |
| 55.0.4 | 0 / 1 | |
| 55.0.3 | 0 / 1 | |
| 55.0.2 | 0 / 1 | |
| 55.0.1 | 0 / 1 | |
| 55.0.0 | 0 / 1 | |
| 14.0.8 | 0 / 1 |
v56.0.4
2 findingsThis 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.
Package 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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v55.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v55.0.9
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. 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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.7
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. 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.6
2 findingsThis version was published by a different npm account than previous versions on 2026-02-16. 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.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
1 findingPackage 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-01-22. 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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.