VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

merge: vulnerability history, versions and safety

merge is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, from Nov 2018 to May 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
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 merge vulnerabilities

Vulert verdict on merge 2.1.1 i

Updated on 23 Oct 2026

Good news: 2.1.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 61/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.1.1 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 04 May 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 9,135 packages i
  • Stars 175 i
  • OpenSSF scorecard 2/10 i
  • Last release 68 months ago i
  • Licence MIT i
  • Similar names merge2 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 merge, 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.1.1 22 Feb 2021 none MIT — Details →
2.1.0 14 Nov 2020 H1 MIT Yes Details →
1.2.1 27 Oct 2018 H1 MIT Yes Details →
1.2.0 07 Sep 2014 H2 MIT Yes Details →
1.1.3 17 Apr 2014 H2 MIT Yes Details →
1.1.2 04 Aug 2013 H2 MIT Yes Details →
1.1.1 10 May 2013 H2 MIT Yes Details →
1.1.0 05 May 2013 H2 MIT Yes Details →
1.0.0 07 May 2012 H2 MIT Yes Details →

All 9 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for merge

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-16469: Prototype Pollution in merge 7.5 high 1.2.1 01 Nov 2018
CVE-2020-28499: Prototype Pollution in merge 7.3 high 2.1.1 04 May 2021

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 merge

Is merge safe to use?

Vulert records 2 vulnerabilities for merge in npm: 0 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is merge's Vulert package health score?

Vulert scores merge 61/100, which reads as usable, but worth attention. 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 merge affected?

No. 2.1.1, 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 merge should I use?

2.1.1 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 merge have?

2 vulnerabilities are recorded for merge in the npm ecosystem: 0 critical, 2 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 merge vulnerabilities disclosed?

0 vulnerabilities were recorded for merge in the last 12 months, and the oldest entry in this database dates to 01 Nov 2018. 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 merge 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 merge for upcoming vulnerabilities?

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