VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@expo/env: vulnerability history, versions and safety

@expo/env 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.

See all @expo/env vulnerabilities

Vulert verdict on @expo/env 2.5.3 i

Updated on 23 Oct 2026

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

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 2.5.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 127 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/env, 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
2.5.3 21 Oct 2026 none MIT — Details →
2.5.2 13 Oct 2026 none MIT — Details →
2.5.1 29 Sep 2026 none MIT — Details →
2.5.0 10 Sep 2026 none MIT — Details →
2.5.0-canary-20260909-ea7a89a 09 Sep 2026 none MIT — Details →
2.5.0-canary-20260902-26df09e 02 Sep 2026 none MIT — Details →
2.4.3 28 Aug 2026 none MIT — Details →
2.5.0-canary-20260812-27f94d4 12 Aug 2026 none MIT — Details →
2.4.3-canary-20260806-8c2d007 06 Aug 2026 none MIT — Details →
2.3.2-canary-20260723-64edab9 23 Jul 2026 none MIT — Details →
2.3.2-canary-20260720-b6d63bc 20 Jul 2026 none MIT — Details →
2.3.2-canary-20260718-7cbcda5 18 Jul 2026 none MIT — Details →
2.3.2-canary-20260716-381e806 16 Jul 2026 none MIT — Details →
2.0.12 15 Jul 2026 none MIT — Details →
2.1.3 15 Jul 2026 none MIT — Details →
2.4.2 15 Jul 2026 none MIT — Details →
2.3.1 03 Jul 2026 none MIT — Details →
2.4.1 03 Jul 2026 none MIT — Details →
2.3.1-canary-20260701-9100865 01 Jul 2026 none MIT — Details →
2.3.1-canary-20260629-3010085 29 Jun 2026 none MIT — Details →
2.4.0 25 Jun 2026 none MIT — Details →
2.3.1-canary-20260624-9d83b81 24 Jun 2026 none MIT — Details →
2.3.1-canary-20260606-4d4666c 06 Jun 2026 none MIT — Details →
2.3.1-canary-20260526-6cd5e37 26 May 2026 none MIT — Details →
2.3.1-canary-20260526-13e89ca 26 May 2026 none MIT — Details →
2.3.0 20 May 2026 none MIT — Details →
2.2.2-canary-20260506-03817f5 06 May 2026 none MIT — Details →
2.2.1 06 May 2026 none MIT — Details →
2.2.1-canary-20260506-1b0052a 06 May 2026 none MIT — Details →
2.2.1-canary-20260506-326540f 06 May 2026 none MIT — Details →
2.2.1-canary-20260506-964f25d 06 May 2026 none MIT — Details →
2.2.0 05 May 2026 none MIT — Details →
2.1.3-canary-20260505-84af74c 05 May 2026 none MIT — Details →
2.1.2 05 May 2026 none MIT — Details →
2.1.2-canary-20260501-15d3529 01 May 2026 none MIT — Details →
2.1.2-canary-20260501-870dcba 01 May 2026 none MIT — Details →
2.1.2-canary-20260429-a5e59cf 29 Apr 2026 none MIT — Details →
2.1.2-canary-20260424-7bedc9d 24 Apr 2026 none MIT — Details →
2.1.2-canary-20260423-c31bd8e 23 Apr 2026 none MIT — Details →
2.1.2-canary-20260420-2ac87c0 20 Apr 2026 none MIT — Details →
2.1.2-canary-20260417-141204f 17 Apr 2026 none MIT — Details →
2.1.2-canary-20260414-e3dbafd 14 Apr 2026 none MIT — Details →
2.1.2-canary-20260409-6fc2991 09 Apr 2026 none MIT — Details →
2.1.2-canary-20260402-9da566b 02 Apr 2026 none MIT — Details →
2.1.2-canary-20260402-87c5ce2 02 Apr 2026 none MIT — Details →
2.1.2-canary-20260401-5e87ef7 01 Apr 2026 none MIT — Details →
2.1.2-canary-20260328-bdc6273 28 Mar 2026 none MIT — Details →
2.1.2-canary-20260328-2049187 28 Mar 2026 none MIT — Details →
2.1.2-canary-20260327-0789fbc 27 Mar 2026 none MIT — Details →
2.1.2-canary-20260305-5163746 05 Mar 2026 none MIT — Details →
2.1.2-canary-20260223-05214f1 23 Feb 2026 none MIT — Details →
2.1.1 16 Feb 2026 none MIT — Details →
2.1.1-canary-20260212-4f61309 12 Feb 2026 none MIT — Details →
2.1.0 08 Feb 2026 none MIT — Details →
2.0.12-canary-20260128-67ce8d5 28 Jan 2026 none MIT — Details →
2.0.11 26 Jan 2026 none MIT — Details →
2.0.10 22 Jan 2026 none MIT — Details →
2.0.9 21 Jan 2026 none MIT — Details →
2.0.9-canary-20260121-a63c0dd 21 Jan 2026 none MIT — Details →
2.0.9-canary-20260120-bb71700 20 Jan 2026 none MIT — Details →
2.0.9-canary-20260119-17896bf 19 Jan 2026 none MIT — Details →
2.0.9-canary-20260119-70f7c28 19 Jan 2026 none MIT — Details →
2.0.9-canary-20260114-d8e19f5 14 Jan 2026 none MIT — Details →
2.0.9-canary-20260105-6b962e6 05 Jan 2026 none MIT — Details →
2.0.9-canary-20251230-fc48ddc 30 Dec 2025 none MIT — Details →
2.0.9-canary-20251223-b83b31e 23 Dec 2025 none MIT — Details →
2.0.9-canary-20251216-3f01dbf 16 Dec 2025 none MIT — Details →
2.0.9-canary-20251216-6e1f9a7 16 Dec 2025 none MIT — Details →
2.0.9-canary-20251212-acb11f2 12 Dec 2025 none MIT — Details →
2.0.9-canary-20251211-7da85ea 11 Dec 2025 none MIT — Details →
2.0.9-canary-20251210-1f163e3 10 Dec 2025 none MIT — Details →
2.0.9-canary-20251206-615dec1 06 Dec 2025 none MIT — Details →
2.0.9-canary-20251205-a1dedc6 05 Dec 2025 none MIT — Details →
2.0.9-canary-20251205-756eb7a 05 Dec 2025 none MIT — Details →
2.0.8 05 Dec 2025 none MIT — Details →
2.0.8-canary-20251127-587bc53 27 Nov 2025 none MIT — Details →
2.0.8-canary-20251120-e46b3cc 20 Nov 2025 none MIT — Details →
2.0.8-canary-20251119-961a032 19 Nov 2025 none MIT — Details →
2.0.8-canary-20251118-8f7ee64 18 Nov 2025 none MIT — Details →
2.0.8-canary-20251031-b135dff 31 Oct 2025 none MIT — Details →
2.0.8-canary-20251023-4c86f95 23 Oct 2025 none MIT — Details →
2.0.8-canary-20251015-a6a1272 15 Oct 2025 none MIT — Details →
2.0.8-canary-20251013-623c5a6 13 Oct 2025 none MIT — Details →
2.0.8-canary-20251009-9919e08 09 Oct 2025 none MIT — Details →
2.0.8-canary-20251008-f2d1b4a 08 Oct 2025 none MIT — Details →
2.0.8-canary-20251008-6acbc1c 08 Oct 2025 none MIT — Details →
2.0.8-canary-20251003-7b9d7ff 03 Oct 2025 none MIT — Details →
2.0.8-canary-20250930-9dc59d3 30 Sep 2025 none MIT — Details →
2.0.8-canary-20250919-7a31b96 19 Sep 2025 none MIT — Details →
2.0.8-canary-20250912-b5ce2a8 12 Sep 2025 none MIT — Details →
2.0.7 10 Sep 2025 none MIT — Details →
2.0.6 02 Sep 2025 none MIT — Details →
2.0.5 31 Aug 2025 none MIT — Details →
2.0.5-canary-20250830-81bb199 30 Aug 2025 none MIT — Details →
2.0.4 27 Aug 2025 none MIT — Details →
2.0.4-canary-20250826-f475166 26 Aug 2025 none MIT — Details →
2.0.3 25 Aug 2025 none MIT — Details →
2.0.2 17 Aug 2025 none MIT — Details →
2.0.1 15 Aug 2025 none MIT — Details →
2.0.0 13 Aug 2025 none MIT — Details →
1.0.8-canary-20250729-d8899ae 29 Jul 2025 none — — Details →
1.0.8-canary-20250722-599a28f 22 Jul 2025 none — — Details →
1.0.8-canary-20250713-8f814f8 13 Jul 2025 none — — Details →
1.0.8-canary-20250709-136b77f 09 Jul 2025 none — — Details →
1.0.7 03 Jul 2025 none — — Details →
1.0.7-canary-20250701-6a945c5 01 Jul 2025 none — — Details →
1.0.6 01 Jul 2025 none — — Details →
1.0.6-canary-20250630-547cd82 30 Jun 2025 none — — Details →
1.0.6-canary-20250613-b29d676 13 Jun 2025 none — — Details →
1.0.6-canary-20250612-338ef55 12 Jun 2025 none — — Details →
1.0.6-canary-20250611-f0afe80 11 Jun 2025 none — — Details →
1.0.5 30 Apr 2025 none — — Details →
1.0.4 25 Apr 2025 none — — Details →
1.0.3 14 Apr 2025 none — — Details →
1.0.2 09 Apr 2025 none — — Details →
1.0.1 08 Apr 2025 none — — Details →
1.0.1-canary-20250408-7f0ab53 08 Apr 2025 none — — Details →
1.0.1-canary-20250407-10a9b42 07 Apr 2025 none — — Details →
1.0.1-canary-20250404-3c3b5fd 04 Apr 2025 none — — Details →
1.0.1-canary-20250404-87e2506 04 Apr 2025 none — — Details →

The newest 120 of 199 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/env

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/env

Is @expo/env safe to use?

Vulert has no vulnerabilities on record for @expo/env 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/env's Vulert package health score?

Vulert scores @expo/env 86/100, which reads as healthy. 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/env affected?

No. 2.5.3, 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/env have?

0 vulnerabilities are recorded for @expo/env 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/env vulnerabilities disclosed?

0 vulnerabilities were recorded for @expo/env 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/env 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/env for upcoming vulnerabilities?

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