← Home

expo-dev-client

Expo Development Client

78
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

idebrentvatneexpoadminexponentbycedrickudochienalanhughestsapetaexpo-botphilplwschurmanfson

Keywords

react-nativeexpoexpo-dev-client

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): kudochien is an established Expo org publisher with strong track record; transition appears legitimate. ai
provenance no-provenance AI (provenance): Expo monorepo packages consistently lack Sigstore provenance; stable false positive for this package. ai
phantom-deps phantom-dep:expo-manifests AI (phantom-deps): Config-only reference in Expo monorepo package; not a runtime import concern. ai
phantom-deps phantom-dep:expo-updates-interface AI (phantom-deps): Config-only reference in Expo monorepo package; not a runtime import concern. ai
phantom-deps phantom-dep:expo-dev-menu-interface AI (phantom-deps): Config-only reference in Expo monorepo package; not a runtime import concern. ai

Versions (showing 78 of 78)

Version Deps Published
57.0.9 5 / 4
57.0.8 5 / 4
57.0.7 5 / 4
57.0.6 5 / 4
57.0.5 5 / 4
57.0.4 5 / 4
57.0.3 5 / 4
57.0.2 5 / 4
57.0.1 5 / 4
57.0.0 5 / 4
56.0.24 5 / 4
56.0.23 5 / 4
56.0.22 5 / 4
56.0.21 5 / 4
56.0.20 5 / 4
56.0.19 5 / 4
56.0.18 5 / 4
56.0.17 5 / 4
56.0.16 5 / 4
56.0.15 5 / 4
56.0.14 5 / 4
56.0.13 5 / 4
56.0.12 5 / 4
56.0.11 5 / 4
56.0.10 5 / 4
56.0.9 5 / 4
56.0.8 5 / 4
56.0.7 5 / 4
56.0.6 5 / 4
56.0.5 5 / 4
56.0.4 5 / 4
56.0.3 5 / 4
56.0.2 5 / 4
56.0.1 5 / 4
56.0.0 5 / 3
55.0.37 5 / 2
55.0.36 5 / 2
55.0.35 5 / 2
55.0.34 5 / 2
55.0.33 5 / 2
55.0.32 5 / 2
55.0.31 5 / 2
55.0.30 5 / 2
55.0.29 5 / 2
55.0.28 5 / 2
55.0.27 5 / 2
55.0.26 5 / 2
55.0.25 5 / 2
55.0.24 5 / 2
55.0.23 5 / 2
55.0.22 5 / 2
55.0.21 5 / 2
55.0.20 5 / 2
55.0.19 5 / 2
55.0.18 5 / 2
55.0.17 5 / 2
55.0.16 5 / 2
55.0.15 5 / 2
55.0.14 5 / 2
55.0.13 5 / 2
55.0.12 5 / 2
55.0.11 5 / 2
55.0.10 5 / 2
55.0.9 5 / 2
55.0.8 5 / 2
55.0.7 5 / 2
55.0.6 5 / 2
55.0.5 5 / 2
55.0.4 5 / 2
55.0.3 5 / 2
55.0.2 5 / 2
55.0.1 5 / 2
55.0.0 5 / 2
6.0.21 5 / 2
6.0.20 5 / 2
6.0.19 5 / 2
6.0.18 5 / 2
6.0.17 5 / 2

v57.0.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v57.0.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v57.0.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v57.0.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v57.0.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v57.0.4

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: brentvatne → alanhughes (on 2026-07-01, known maintainer) provenance

This version was published by a different npm account (alanhughes) than the most recent previously approved version (brentvatne) on 2026-07-01, 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.

v57.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v57.0.2

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: alanhughes → brentvatne (on 2026-06-27, known maintainer) provenance

This version was published by a different npm account (brentvatne) than the most recent previously approved version (alanhughes) on 2026-06-27, 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.24

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v56.0.23

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v56.0.22

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v56.0.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v55.0.37

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.