Vulnerability Database · npm · Package report

expo-dev-client: vulnerability history, versions and safety

expo-dev-client is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on expo-dev-client 58.0.14 i

Updated on 23 Oct 2026

Good news: 58.0.14, the version you would install today, has no known vulnerabilities.

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

What to do: Stay on 58.0.14 or newer. This can change: a vulnerability disclosed tomorrow can affect 58.0.14 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 58.0.14 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 52,895 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for expo-dev-client, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
55.0.41 21 Oct 2026 none MIT — Details →
56.0.28 21 Oct 2026 none MIT — Details →
58.0.14 16 Oct 2026 none MIT — Details →
58.0.13 13 Oct 2026 none MIT — Details →
57.0.20 12 Oct 2026 none MIT — Details →
58.0.12 09 Oct 2026 none MIT — Details →
58.0.11 03 Oct 2026 none MIT — Details →
58.0.10 01 Oct 2026 none MIT — Details →
58.0.9 29 Sep 2026 none MIT — Details →
58.0.8 28 Sep 2026 none MIT — Details →
58.0.7 25 Sep 2026 none MIT — Details →
58.0.6 23 Sep 2026 none MIT — Details →
58.0.5 22 Sep 2026 none MIT — Details →
58.0.4 21 Sep 2026 none MIT — Details →
56.0.27 17 Sep 2026 none MIT — Details →
58.0.3 16 Sep 2026 none MIT — Details →
58.0.2 15 Sep 2026 none MIT — Details →
58.0.1 14 Sep 2026 none MIT — Details →
57.0.19 11 Sep 2026 none MIT — Details →
58.0.0 10 Sep 2026 none MIT — Details →
58.0.0-canary-20260909-ea7a89a 09 Sep 2026 none MIT — Details →
58.0.0-canary-20260902-26df09e 02 Sep 2026 none MIT — Details →
58.0.0-canary-20260901-2164f24 02 Sep 2026 none MIT — Details →
57.0.18 01 Sep 2026 none MIT — Details →
57.0.17 01 Sep 2026 none MIT — Details →
55.0.40 31 Aug 2026 none MIT — Details →
56.0.26 28 Aug 2026 none MIT — Details →
57.0.16 26 Aug 2026 none MIT — Details →
55.0.39 25 Aug 2026 none MIT — Details →
57.0.15 24 Aug 2026 none MIT — Details →
57.0.14 20 Aug 2026 none MIT — Details →
55.0.38 17 Aug 2026 none MIT — Details →
56.0.25 17 Aug 2026 none MIT — Details →
57.0.13 17 Aug 2026 none MIT — Details →
57.0.12 14 Aug 2026 none MIT — Details →
58.0.0-canary-20260812-27f94d4 12 Aug 2026 none MIT — Details →
57.0.11 10 Aug 2026 none MIT — Details →
58.0.0-canary-20260806-8c2d007 06 Aug 2026 none MIT — Details →
57.0.10 29 Jul 2026 none MIT — Details →
57.0.0-canary-20260723-64edab9 23 Jul 2026 none MIT — Details →
57.0.9 23 Jul 2026 none MIT — Details →
56.0.24 23 Jul 2026 none MIT — Details →
57.0.8 22 Jul 2026 none MIT — Details →
57.0.0-canary-20260720-b6d63bc 20 Jul 2026 none MIT — Details →
57.0.0-canary-20260718-7cbcda5 18 Jul 2026 none MIT — Details →
57.0.7 17 Jul 2026 none MIT — Details →
57.0.0-canary-20260716-381e806 16 Jul 2026 none MIT — Details →
55.0.37 15 Jul 2026 none MIT — Details →
56.0.23 15 Jul 2026 none MIT — Details →
57.0.6 15 Jul 2026 none MIT — Details →
56.0.22 03 Jul 2026 none MIT — Details →
57.0.5 03 Jul 2026 none MIT — Details →
56.0.17-canary-20260701-9100865 01 Jul 2026 none MIT — Details →
56.0.21 01 Jul 2026 none MIT — Details →
57.0.4 01 Jul 2026 none MIT — Details →
57.0.3 30 Jun 2026 none MIT — Details →
57.0.0-canary-20260629-3010085 29 Jun 2026 none MIT — Details →
57.0.2 27 Jun 2026 none MIT — Details →
57.0.1 25 Jun 2026 none MIT — Details →
57.0.0 25 Jun 2026 none MIT — Details →
55.0.36 25 Jun 2026 none MIT — Details →
56.0.17-canary-20260624-9d83b81 24 Jun 2026 none MIT — Details →
56.0.20 10 Jun 2026 none MIT — Details →
56.0.17-canary-20260606-4d4666c 06 Jun 2026 none MIT — Details →
56.0.19 05 Jun 2026 none MIT — Details →
56.0.18 29 May 2026 none MIT — Details →
56.0.17 29 May 2026 none MIT — Details →
56.0.17-canary-20260526-6cd5e37 26 May 2026 none MIT — Details →
56.0.16 26 May 2026 none MIT — Details →
57.0.0-canary-20260526-13e89ca 26 May 2026 none MIT — Details →
56.0.15 23 May 2026 none MIT — Details →
56.0.14 21 May 2026 none MIT — Details →
56.0.13 20 May 2026 none MIT — Details →
55.0.35 19 May 2026 none MIT — Details →
56.0.12 19 May 2026 none MIT — Details →
56.0.11 15 May 2026 none MIT — Details →
55.0.34 15 May 2026 none MIT — Details →
56.0.10 14 May 2026 none MIT — Details →
56.0.9 13 May 2026 none MIT — Details →
56.0.8 13 May 2026 none MIT — Details →
56.0.7 13 May 2026 none MIT — Details →
55.0.33 13 May 2026 none MIT — Details →
56.0.6 11 May 2026 none MIT — Details →
56.0.5 08 May 2026 none MIT — Details →
56.0.4 07 May 2026 none MIT — Details →
56.0.0-canary-20260506-03817f5 06 May 2026 none MIT — Details →
56.0.3 06 May 2026 none MIT — Details →
56.0.2 06 May 2026 none MIT — Details →
56.0.1 06 May 2026 none MIT — Details →
56.0.0-canary-20260506-1b0052a 06 May 2026 none MIT — Details →
56.0.0-canary-20260506-326540f 06 May 2026 none MIT — Details →
56.0.0-canary-20260506-964f25d 06 May 2026 none MIT — Details →
56.0.0 05 May 2026 none MIT — Details →
56.0.0-canary-20260505-84af74c 05 May 2026 none MIT — Details →
56.0.0-canary-20260505-d2856c3 05 May 2026 none MIT — Details →
55.0.32 04 May 2026 none MIT — Details →
55.0.31 04 May 2026 none MIT — Details →
56.0.0-canary-20260504-8fccdbb 04 May 2026 none MIT — Details →
56.0.0-canary-20260501-15d3529 01 May 2026 none MIT — Details →
56.0.0-canary-20260501-870dcba 01 May 2026 none MIT — Details →
55.0.30 01 May 2026 none — — Details →
55.0.29 01 May 2026 none — — Details →
55.0.10-canary-20260429-a5e59cf 29 Apr 2026 none — — Details →
6.0.21 27 Apr 2026 none — — Details →
55.0.10-canary-20260424-7bedc9d 24 Apr 2026 none — — Details →
56.0.0-canary-20260423-c31bd8e 23 Apr 2026 none — — Details →
55.0.28 21 Apr 2026 none — — Details →
56.0.0-canary-20260420-2ac87c0 20 Apr 2026 none — — Details →
56.0.0-canary-20260417-141204f 17 Apr 2026 none — — Details →
56.0.0-canary-20260414-e3dbafd 14 Apr 2026 none — — Details →
55.0.27 11 Apr 2026 none — — Details →
55.0.26 10 Apr 2026 none — — Details →
55.0.25 10 Apr 2026 none — — Details →
56.0.0-canary-20260409-6fc2991 09 Apr 2026 none — — Details →
55.0.24 09 Apr 2026 none — — Details →
55.0.23 07 Apr 2026 none — — Details →
55.0.22 02 Apr 2026 none — — Details →
55.0.21 02 Apr 2026 none — — Details →
55.0.20 02 Apr 2026 none — — Details →
55.0.20-canary-20260402-9da566b 02 Apr 2026 none — — Details →

The newest 120 of 444 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for expo-dev-client

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About expo-dev-client

Is expo-dev-client safe to use?

Vulert has no vulnerabilities on record for expo-dev-client in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is expo-dev-client's Vulert package health score?

Vulert scores expo-dev-client 82/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of expo-dev-client affected?

No. 58.0.14, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does expo-dev-client have?

0 vulnerabilities are recorded for expo-dev-client in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new expo-dev-client vulnerabilities disclosed?

0 vulnerabilities were recorded for expo-dev-client in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of expo-dev-client are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor expo-dev-client for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the expo-dev-client version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.