VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

dotenv-expand: vulnerability history, versions and safety

dotenv-expand 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 dotenv-expand vulnerabilities

Vulert verdict on dotenv-expand 1000.0.0 i

Updated on 23 Oct 2026

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

Package health score 88/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 1000.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 172 packages i
  • Stars 1,056 i
  • Last release 2 months ago i
  • Licence BSD-3-Clause 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 dotenv-expand, 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
1000.0.0 29 Jul 2026 none BSD-3-Clause — Details →
13.0.0 17 Apr 2026 none BSD-2-Clause — Details →
12.0.3 02 Sep 2025 none BSD-2-Clause — Details →
12.0.2 17 Apr 2025 none BSD-2-Clause — Details →
12.0.1 18 Nov 2024 none BSD-2-Clause — Details →
12.0.0 16 Nov 2024 none BSD-2-Clause — Details →
11.0.7 13 Nov 2024 none BSD-2-Clause — Details →
11.0.6 18 Feb 2024 none BSD-2-Clause — Details →
11.0.5 18 Feb 2024 none BSD-2-Clause — Details →
11.0.4 15 Feb 2024 none BSD-2-Clause — Details →
11.0.3 11 Feb 2024 none BSD-2-Clause — Details →
11.0.2 10 Feb 2024 none BSD-2-Clause — Details →
11.0.1 10 Feb 2024 none BSD-2-Clause — Details →
11.0.0 10 Feb 2024 none BSD-2-Clause — Details →
10.0.0 16 Dec 2022 none BSD-2-Clause — Details →
9.0.0 30 Aug 2022 none BSD-2-Clause — Details →
8.0.3 21 Mar 2022 none BSD-2-Clause — Details →
8.0.2 11 Mar 2022 none BSD-2-Clause — Details →
8.0.1 04 Feb 2022 none BSD-2-Clause — Details →
8.0.0 04 Feb 2022 none BSD-2-Clause — Details →
7.0.0 02 Feb 2022 none BSD-2-Clause — Details →
6.0.1 17 Jan 2022 none BSD-2-Clause — Details →
6.0.0 17 Jan 2022 none BSD-2-Clause — Details →
5.1.0 18 Mar 2019 none BSD-2-Clause — Details →
5.0.0 13 Mar 2019 none BSD-2-Clause — Details →
4.2.0 08 Feb 2018 none BSD-2-Clause — Details →
4.1.0 08 Feb 2018 none BSD-2-Clause — Details →
4.0.1 31 Mar 2017 none BSD-2-Clause — Details →
4.0.0 31 Mar 2017 none BSD-2-Clause — Details →
0.1.0 21 Jan 2016 none BSD-2-Clause — Details →

All 30 versions Vulert tracks for this package. 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 dotenv-expand

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 dotenv-expand

Is dotenv-expand safe to use?

Vulert has no vulnerabilities on record for dotenv-expand 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 dotenv-expand's Vulert package health score?

Vulert scores dotenv-expand 88/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 dotenv-expand affected?

No. 1000.0.0, 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 dotenv-expand should I use?

1000.0.0 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 dotenv-expand have?

0 vulnerabilities are recorded for dotenv-expand 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 dotenv-expand vulnerabilities disclosed?

0 vulnerabilities were recorded for dotenv-expand 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 dotenv-expand 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 dotenv-expand for upcoming vulnerabilities?

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