VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@corex/deepmerge: vulnerability history, versions and safety

@corex/deepmerge 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 @corex/deepmerge vulnerabilities

Vulert verdict on @corex/deepmerge 4.0.43 i

Updated on 23 Oct 2026

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

Package health score 72/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Not enough data

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

  • Current release 4.0.43 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 65 packages i
  • Last release 42 months 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 @corex/deepmerge, 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
4.0.43 12 Apr 2023 none MIT — Details →
4.0.37 10 Jan 2023 none MIT — Details →
4.0.29 29 Jun 2022 none MIT — Details →
4.0.26 20 Jun 2022 none MIT — Details →
4.0.24 19 Jun 2022 none MIT — Details →
4.0.22 13 Jun 2022 none MIT — Details →
4.0.19 13 Jun 2022 none MIT — Details →
4.0.18 13 Jun 2022 none MIT — Details →
4.0.16 03 Jun 2022 none MIT — Details →
4.0.14 31 May 2022 none MIT — Details →
4.0.12 31 May 2022 none MIT — Details →
4.0.11 31 May 2022 none MIT — Details →
4.0.9 31 May 2022 none MIT — Details →
3.0.611 29 May 2022 none MIT — Details →
3.0.600 29 May 2022 none MIT — Details →
3.0.560 04 Apr 2022 none MIT — Details →
3.0.545 24 Mar 2022 none MIT — Details →
3.0.542 24 Mar 2022 none MIT — Details →
3.0.539 21 Mar 2022 none MIT — Details →
3.0.535 21 Mar 2022 none MIT — Details →
3.0.530 21 Mar 2022 none MIT — Details →
3.0.524 21 Mar 2022 none MIT — Details →
3.0.517 15 Mar 2022 none MIT — Details →
3.0.515 15 Mar 2022 none MIT — Details →
3.0.512 15 Mar 2022 none MIT — Details →
3.0.508 15 Mar 2022 none MIT — Details →
3.0.503 15 Mar 2022 none MIT — Details →
3.0.497 15 Mar 2022 none MIT — Details →
3.0.490 15 Mar 2022 none MIT — Details →
3.0.482 15 Mar 2022 none MIT — Details →
3.0.473 07 Mar 2022 none MIT — Details →
3.0.471 07 Mar 2022 none MIT — Details →
3.0.468 07 Mar 2022 none MIT — Details →
3.0.464 07 Mar 2022 none MIT — Details →
3.0.459 07 Mar 2022 none MIT — Details →
3.0.453 02 Mar 2022 none MIT — Details →
3.0.451 02 Mar 2022 none MIT — Details →
3.0.448 02 Mar 2022 none MIT — Details →
3.0.444 02 Mar 2022 none MIT — Details →
3.0.439 02 Mar 2022 none MIT — Details →
3.0.433 02 Mar 2022 none MIT — Details →
3.0.426 02 Mar 2022 none MIT — Details →
3.0.418 02 Mar 2022 none MIT — Details →
3.0.409 02 Mar 2022 none MIT — Details →
3.0.399 02 Mar 2022 none MIT — Details →
3.0.388 02 Mar 2022 none MIT — Details →
3.0.377 02 Mar 2022 none MIT — Details →
3.0.366 02 Mar 2022 none MIT — Details →
3.0.355 02 Mar 2022 none MIT — Details →
3.0.340 18 Feb 2022 none MIT — Details →
3.0.337 14 Feb 2022 none MIT — Details →
3.0.335 14 Feb 2022 none MIT — Details →
3.0.332 14 Feb 2022 none MIT — Details →
3.0.328 14 Feb 2022 none MIT — Details →
3.0.323 14 Feb 2022 none MIT — Details →
3.0.317 14 Feb 2022 none MIT — Details →
3.0.310 14 Feb 2022 none MIT — Details →
3.0.302 14 Feb 2022 none MIT — Details →
3.0.293 07 Feb 2022 none MIT — Details →
3.0.291 07 Feb 2022 none MIT — Details →
3.0.288 07 Feb 2022 none MIT — Details →
3.0.284 07 Feb 2022 none MIT — Details →
3.0.279 07 Feb 2022 none MIT — Details →
3.0.273 07 Feb 2022 none MIT — Details →
3.0.266 07 Feb 2022 none MIT — Details →
3.0.258 07 Feb 2022 none MIT — Details →
3.0.249 31 Jan 2022 none MIT — Details →
3.0.247 31 Jan 2022 none MIT — Details →
3.0.244 31 Jan 2022 none MIT — Details →
3.0.240 31 Jan 2022 none MIT — Details →
3.0.235 31 Jan 2022 none MIT — Details →
3.0.229 31 Jan 2022 none MIT — Details →
3.0.222 31 Jan 2022 none MIT — Details →
3.0.214 31 Jan 2022 none MIT — Details →
3.0.205 31 Jan 2022 none MIT — Details →
3.0.195 31 Jan 2022 none MIT — Details →
3.0.176 12 Jan 2022 none MIT — Details →
3.0.170 09 Jan 2022 none MIT — Details →
2.6.148 14 Dec 2021 none MIT — Details →
2.6.133 03 Dec 2021 none MIT — Details →
2.6.110 03 Dec 2021 none MIT — Details →
2.6.34 14 Aug 2021 none MIT — Details →
2.6.20 18 May 2021 none MIT — Details →
2.5.11 07 May 2021 none MIT — Details →
2.5.9 29 Apr 2021 none MIT — Details →
2.5.6 16 Mar 2021 none MIT — Details →
2.5.3 15 Dec 2020 none MIT — Details →
2.4.24 25 Oct 2020 none MIT — Details →
2.4.20 25 Oct 2020 none MIT — Details →
2.4.17 10 Oct 2020 none MIT — Details →
2.4.14 22 Sep 2020 none MIT — Details →
2.4.9 05 Sep 2020 none MIT — Details →
2.4.6 30 Aug 2020 none MIT — Details →
2.3.6 14 Aug 2020 none MIT — Details →
2.3.5 14 Aug 2020 none MIT — Details →
2.3.4 14 Aug 2020 none MIT — Details →
2.3.3 14 Aug 2020 none MIT — Details →
2.3.2 14 Aug 2020 none MIT — Details →
2.3.1 13 Aug 2020 none MIT — Details →
2.2.15 13 Aug 2020 none MIT — Details →
2.2.14 13 Aug 2020 none — — Details →
2.2.13 13 Aug 2020 none — — Details →
2.2.12 11 Aug 2020 none — — Details →
2.2.11 11 Aug 2020 none — — Details →
2.2.10 11 Aug 2020 none — — Details →
2.2.9 10 Aug 2020 none — — Details →
2.2.8 10 Aug 2020 none — — Details →
2.2.7 10 Aug 2020 none — — Details →
2.2.6 09 Aug 2020 none — — Details →
2.2.5 09 Aug 2020 none — — Details →

All 110 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 @corex/deepmerge

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 @corex/deepmerge

Is @corex/deepmerge safe to use?

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

Vulert scores @corex/deepmerge 72/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 @corex/deepmerge affected?

No. 4.0.43, 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 @corex/deepmerge should I use?

4.0.43 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 @corex/deepmerge have?

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

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

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