Vulnerability Database · npm · Package report
expo-device: vulnerability history, versions and safety
expo-device is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on expo-device 57.0.2 i
Updated on 23 Oct 2026
Good news: 57.0.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Widely used
- Community Moderate
What to do: Stay on 57.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 57.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 57.0.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 29 packages i
- Stars 52,895 i
- OpenSSF scorecard 4/10 i
- Last release 1 month ago 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-device, 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.
- 58.0.5 01 Oct 2026
- 58.0.4 01 Oct 2026
- 58.0.3 29 Sep 2026
- 58.0.2 22 Sep 2026
- 58.0.1 21 Sep 2026
- 57.0.2 11 Sep 2026
- 58.0.0 10 Sep 2026
- 58.0.0-canary-20260909-ea7a89a 09 Sep 2026
- 58.0.0-canary-20260902-26df09e 02 Sep 2026
- 58.0.0-canary-20260901-2164f24 02 Sep 2026
- 55.0.21 25 Aug 2026
- 55.0.20 17 Aug 2026
- 58.0.0-canary-20260812-27f94d4 12 Aug 2026
- 58.0.0-canary-20260806-8c2d007 06 Aug 2026
- 57.0.0-canary-20260723-64edab9 23 Jul 2026
- 57.0.0-canary-20260720-b6d63bc 20 Jul 2026
- 57.0.0-canary-20260718-7cbcda5 18 Jul 2026
- 57.0.0-canary-20260716-381e806 16 Jul 2026
- 55.0.19 15 Jul 2026
- 57.0.1 15 Jul 2026
- 56.0.5-canary-20260701-9100865 01 Jul 2026
- 57.0.0-canary-20260629-3010085 29 Jun 2026
- 57.0.0 25 Jun 2026
- 55.0.18 25 Jun 2026
- 56.0.5-canary-20260624-9d83b81 24 Jun 2026
- 56.0.5-canary-20260606-4d4666c 06 Jun 2026
- 56.0.5-canary-20260526-6cd5e37 26 May 2026
- 57.0.0-canary-20260526-13e89ca 26 May 2026
- 55.0.17 13 May 2026
- 56.0.0-canary-20260506-03817f5 06 May 2026
- 56.0.4 06 May 2026
- 56.0.3 06 May 2026
- 56.0.2 06 May 2026
- 56.0.0-canary-20260506-1b0052a 06 May 2026
- 56.0.0-canary-20260506-326540f 06 May 2026
- 56.0.0-canary-20260506-964f25d 06 May 2026
- 56.0.1 05 May 2026
- 56.0.0 05 May 2026
- 56.0.0-canary-20260505-84af74c 05 May 2026
- 55.0.16 05 May 2026
- 56.0.0-canary-20260505-d2856c3 05 May 2026
- 56.0.0-canary-20260504-8fccdbb 04 May 2026
- 56.0.0-canary-20260501-15d3529 01 May 2026
- 56.0.0-canary-20260501-870dcba 01 May 2026
- 55.0.10-canary-20260429-a5e59cf 29 Apr 2026
- 55.0.10-canary-20260424-7bedc9d 24 Apr 2026
- 56.0.0-canary-20260423-c31bd8e 23 Apr 2026
- 56.0.0-canary-20260420-2ac87c0 20 Apr 2026
- 56.0.0-canary-20260417-141204f 17 Apr 2026
- 56.0.0-canary-20260414-e3dbafd 14 Apr 2026
- 55.0.15 13 Apr 2026
- 56.0.0-canary-20260409-6fc2991 09 Apr 2026
- 55.0.14 09 Apr 2026
- 55.0.13 07 Apr 2026
- 55.0.12 02 Apr 2026
- 55.0.11 02 Apr 2026
- 55.0.11-canary-20260402-9da566b 02 Apr 2026
- 56.0.0-canary-20260402-87c5ce2 02 Apr 2026
- 55.0.11-canary-20260401-5e87ef7 01 Apr 2026
- 55.0.11-canary-20260328-bdc6273 28 Mar 2026
- 55.0.11-canary-20260328-2049187 28 Mar 2026
- 55.0.11-canary-20260327-0789fbc 27 Mar 2026
- 55.0.10 17 Mar 2026
- 56.0.0-canary-20260305-5163746 05 Mar 2026
- 55.0.9 25 Feb 2026
- 55.0.0-canary-20260223-05214f1 23 Feb 2026
- 55.0.8 20 Feb 2026
- 55.0.7 16 Feb 2026
- 56.0.0-canary-20260212-4f61309 12 Feb 2026
- 55.0.6 08 Feb 2026
- 55.0.5 03 Feb 2026
- 55.0.4 03 Feb 2026
- 55.0.4-canary-20260128-67ce8d5 28 Jan 2026
- 55.0.3 27 Jan 2026
- 55.0.2 26 Jan 2026
- 55.0.1 22 Jan 2026
- 55.0.0 21 Jan 2026
- 8.0.11-canary-20260121-a63c0dd 21 Jan 2026
- 8.0.11-canary-20260120-bb71700 20 Jan 2026
- 8.0.11-canary-20260119-17896bf 19 Jan 2026
- 8.0.11-canary-20260119-70f7c28 19 Jan 2026
- 8.0.11-canary-20260114-d8e19f5 14 Jan 2026
- 8.0.11-canary-20260113-4879b86 13 Jan 2026
- 8.0.11-canary-20260113-0ce2b9c 13 Jan 2026
- 8.0.11-canary-20260105-6b962e6 05 Jan 2026
- 8.0.11-canary-20251230-fc48ddc 30 Dec 2025
- 8.0.11-canary-20251223-b83b31e 23 Dec 2025
- 8.0.11-canary-20251216-3f01dbf 16 Dec 2025
- 8.0.11-canary-20251216-6e1f9a7 16 Dec 2025
- 8.0.11-canary-20251212-acb11f2 12 Dec 2025
- 8.0.11-canary-20251211-7da85ea 11 Dec 2025
- 8.0.11-canary-20251210-1f163e3 10 Dec 2025
- 8.0.11-canary-20251206-615dec1 06 Dec 2025
- 8.0.11-canary-20251205-a1dedc6 05 Dec 2025
- 8.0.11-canary-20251205-756eb7a 05 Dec 2025
- 8.0.10 05 Dec 2025
- 8.0.10-canary-20251127-587bc53 27 Nov 2025
- 8.0.10-canary-20251120-e46b3cc 20 Nov 2025
- 8.0.10-canary-20251119-961a032 19 Nov 2025
- 8.0.10-canary-20251118-8f7ee64 18 Nov 2025
- 8.0.10-canary-20251118-4ca99d5 18 Nov 2025
- 8.0.10-canary-20251031-b135dff 31 Oct 2025
- 8.0.10-canary-20251023-4c86f95 23 Oct 2025
- 8.0.10-canary-20251015-a6a1272 15 Oct 2025
- 8.0.10-canary-20251013-623c5a6 13 Oct 2025
- 8.0.10-canary-20251009-9919e08 09 Oct 2025
- 8.0.10-canary-20251008-f2d1b4a 08 Oct 2025
- 8.0.10-canary-20251008-6acbc1c 08 Oct 2025
- 8.0.10-canary-20251003-7b9d7ff 03 Oct 2025
- 8.0.9 01 Oct 2025
- 8.1.0-canary-20250930-9dc59d3 30 Sep 2025
- 8.1.0-canary-20250919-7a31b96 19 Sep 2025
- 8.0.8 18 Sep 2025
- 8.0.8-canary-20250912-b5ce2a8 12 Sep 2025
- 8.0.7 11 Sep 2025
- 8.0.6 02 Sep 2025
- 8.0.5 31 Aug 2025
- 8.0.5-canary-20250830-81bb199 30 Aug 2025
- 8.0.4 27 Aug 2025
- 8.0.4-canary-20250826-f475166 26 Aug 2025
The newest 120 of 248 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for expo-device
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
Questions
About expo-device
Is expo-device safe to use?
Vulert has no vulnerabilities on record for expo-device 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-device's Vulert package health score?
Vulert scores expo-device 84/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-device affected?
No. 57.0.2, 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.
Which version of expo-device should I use?
57.0.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does expo-device have?
0 vulnerabilities are recorded for expo-device 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-device vulnerabilities disclosed?
0 vulnerabilities were recorded for expo-device 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-device 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-device for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the expo-device version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.