expo-sharing
Provides a way to share files directly with other compatible applications.
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 core Expo maintainer; publisher rotation within the Expo org is normal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Expo team roster changes are routine; brentvatne is a longstanding core maintainer. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Artifact of Expo SDK version numbering jump (14→55), not true dormancy. | ai | |
| dependencies | unvetted-dep:@expo/plist | AI (dependencies): @expo/plist is a first-party Expo package from 650 Industries; stable dependency for all expo-sharing versions. | ai | |
| dependencies | unvetted-dep:@expo/config-types | AI (dependencies): @expo/config-types is a first-party Expo package from 650 Industries; stable dependency for all expo-sharing versions. | ai | |
| dependencies | unvetted-dep:@expo/config-plugins | AI (dependencies): @expo/config-plugins is a first-party Expo package from 650 Industries; stable dependency for all expo-sharing versions. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 56.0.17 | 3 / 4 | |
| 56.0.16 | 3 / 4 | |
| 56.0.15 | 3 / 4 | |
| 56.0.14 | 3 / 4 | |
| 56.0.13 | 3 / 4 | |
| 56.0.12 | 3 / 4 | |
| 56.0.11 | 3 / 4 | |
| 56.0.10 | 3 / 4 | |
| 56.0.9 | 3 / 4 | |
| 56.0.8 | 3 / 4 | |
| 56.0.7 | 3 / 4 | |
| 56.0.6 | 3 / 4 | |
| 56.0.5 | 3 / 4 | |
| 56.0.4 | 3 / 4 | |
| 56.0.3 | 3 / 4 | |
| 56.0.2 | 3 / 4 | |
| 56.0.1 | 3 / 4 | |
| 56.0.0 | 3 / 3 | |
| 55.0.20 | 3 / 1 | |
| 55.0.19 | 3 / 1 | |
| 55.0.18 | 3 / 1 | |
| 55.0.17 | 3 / 1 | |
| 55.0.16 | 3 / 1 | |
| 55.0.15 | 3 / 1 | |
| 55.0.12 | 3 / 1 | |
| 55.0.11 | 3 / 1 | |
| 55.0.0 | 3 / 1 | |
| 14.0.8 | 0 / 1 |
v56.0.17
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-06-10, 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.16
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 (brentvatne) than the most recent previously approved version (alanhughes) on 2026-06-05, but brentvatne 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.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.12
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.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.19
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v55.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v55.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v55.0.12
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.11
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. 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-01-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.
v14.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.