expo-auth-session
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Official Expo SDK package; provenance not yet adopted by the expo monorepo publish pipeline. | ai | |
| dependencies | unvetted-dep:expo-application | AI (dependencies): expo-application is a sibling Expo SDK package from the same monorepo and publisher. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 57.0.5 | 6 / 3 | |
| 57.0.4 | 6 / 3 | |
| 57.0.3 | 6 / 3 | |
| 57.0.2 | 6 / 3 | |
| 57.0.1 | 6 / 3 | |
| 57.0.0 | 6 / 3 | |
| 56.0.16 | 6 / 3 | |
| 56.0.15 | 6 / 3 | |
| 56.0.14 | 6 / 3 | |
| 56.0.13 | 6 / 3 | |
| 56.0.12 | 6 / 3 | |
| 56.0.11 | 6 / 3 | |
| 56.0.10 | 6 / 3 | |
| 56.0.9 | 6 / 3 | |
| 56.0.8 | 6 / 3 | |
| 56.0.7 | 6 / 3 | |
| 56.0.6 | 6 / 3 | |
| 56.0.5 | 6 / 3 | |
| 56.0.4 | 6 / 3 | |
| 56.0.3 | 6 / 3 | |
| 56.0.2 | 6 / 3 | |
| 56.0.1 | 6 / 3 | |
| 56.0.0 | 6 / 3 | |
| 55.0.17 | 6 / 1 | |
| 55.0.16 | 6 / 1 | |
| 55.0.15 | 6 / 1 | |
| 55.0.14 | 6 / 1 | |
| 55.0.13 | 6 / 1 | |
| 55.0.12 | 6 / 1 | |
| 55.0.11 | 6 / 1 | |
| 55.0.10 | 6 / 1 | |
| 55.0.9 | 6 / 1 | |
| 55.0.8 | 6 / 1 | |
| 55.0.7 | 6 / 1 | |
| 55.0.5 | 6 / 1 | |
| 7.0.11 | 6 / 1 | |
| 7.0.9 | 6 / 1 |
v57.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.1
2 findings[Accepted risk] Package 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-30, 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.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.15
2 findings[Accepted risk] Package 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-07-03, 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.