expo-asset
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by major version cadence in the Expo SDK; brentvatne is a verified Expo org maintainer. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 56.0.17 | 2 / 6 | |
| 56.0.16 | 2 / 6 | |
| 56.0.15 | 2 / 6 | |
| 56.0.14 | 2 / 6 | |
| 56.0.13 | 2 / 6 | |
| 56.0.12 | 2 / 6 | |
| 56.0.11 | 2 / 6 | |
| 56.0.10 | 2 / 6 | |
| 56.0.9 | 2 / 6 | |
| 56.0.8 | 2 / 6 | |
| 56.0.7 | 2 / 6 | |
| 56.0.6 | 2 / 6 | |
| 56.0.5 | 2 / 6 | |
| 56.0.4 | 2 / 6 | |
| 56.0.3 | 2 / 6 | |
| 56.0.2 | 2 / 6 | |
| 56.0.1 | 2 / 5 | |
| 56.0.0 | 2 / 5 | |
| 55.0.17 | 2 / 4 | |
| 55.0.16 | 2 / 4 | |
| 55.0.15 | 2 / 4 | |
| 55.0.14 | 2 / 4 | |
| 55.0.13 | 2 / 4 | |
| 55.0.12 | 2 / 4 | |
| 55.0.11 | 2 / 4 | |
| 55.0.8 | 2 / 4 | |
| 55.0.7 | 2 / 4 | |
| 55.0.4 | 2 / 4 | |
| 55.0.3 | 2 / 4 | |
| 55.0.2 | 2 / 4 | |
| 55.0.1 | 2 / 4 | |
| 55.0.0 | 2 / 4 | |
| 12.0.13 | 2 / 4 | |
| 12.0.12 | 2 / 4 | |
| 12.0.10 | 2 / 4 |
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
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.13
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.12
1 findingPackage 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
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.8
1 findingPackage 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.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.