VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

babel-plugin-minify-mangle-names: vulnerability history, versions and safety

babel-plugin-minify-mangle-names 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 babel-plugin-minify-mangle-names vulnerabilities

Vulert verdict on babel-plugin-minify-mangle-names 0.5.1 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 0.5.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,657 packages i
  • Stars 4,368 i
  • OpenSSF scorecard 2/10 i
  • Last release 53 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 babel-plugin-minify-mangle-names, 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
0.5.1 06 May 2022 none MIT — Details →
0.5.0 24 Sep 2018 none MIT — Details →
0.5.0-alpha.9 23 Sep 2018 none MIT — Details →
0.5.0-alpha.3cc09dcf 27 Jul 2018 none MIT — Details →
0.5.0-alpha.beb87b9a 26 Jul 2018 none MIT — Details →
0.5.0-alpha.5a128fd5 17 Jul 2018 none MIT — Details →
0.5.0-alpha.2ed85317 17 Jul 2018 none MIT — Details →
0.5.0-alpha.a24dd066 11 Jun 2018 none MIT — Details →
0.5.0-alpha.2e0de171 01 Jun 2018 none MIT — Details →
0.5.0-alpha.89fc69da 01 Jun 2018 none MIT — Details →
0.5.0-alpha.a28b6b00 22 May 2018 none MIT — Details →
0.5.0-alpha.2ec8ff72 22 May 2018 none MIT — Details →
0.5.0-alpha.01eac1c3 17 May 2018 none MIT — Details →
0.5.0-alpha.5dbc73f7 17 May 2018 none MIT — Details →
0.5.0-alpha.830ce3f1 17 May 2018 none MIT — Details →
0.5.0-alpha.9e447f6d 17 May 2018 none MIT — Details →
0.5.0-alpha.3b1a8f05 17 May 2018 none MIT — Details →
0.5.0-alpha.367cc048 16 May 2018 none MIT — Details →
0.5.0-alpha.36b27d42 16 May 2018 none MIT — Details →
0.5.0-alpha.7ba5821f 16 May 2018 none MIT — Details →
0.5.0-alpha.7195fa98 16 May 2018 none MIT — Details →
0.5.0-alpha.1cb46b73 16 May 2018 none MIT — Details →
0.5.0-alpha.85c9b6d8 15 May 2018 none MIT — Details →
0.5.0-alpha.6889f45d 14 May 2018 none MIT — Details →
0.5.0-alpha.91ed3622 14 May 2018 none MIT — Details →
0.4.3 14 May 2018 none MIT — Details →
0.5.0-alpha.b5637c57 14 May 2018 none MIT — Details →
0.4.2 14 May 2018 none MIT — Details →
0.5.0-alpha.540d75e7 14 May 2018 none MIT — Details →
0.5.0-alpha.bce578e2 14 May 2018 none MIT — Details →
0.5.0-alpha.18dcfe13 14 May 2018 none MIT — Details →
0.5.0-alpha.9939bca9 13 May 2018 none MIT — Details →
0.5.0-alpha.5f601890 10 May 2018 none MIT — Details →
0.5.0-alpha.34c3efe9 04 May 2018 none MIT — Details →
0.5.0-alpha.9e986477 04 May 2018 none MIT — Details →
0.5.0-alpha.e86a44f1 03 May 2018 none MIT — Details →
0.4.1 03 May 2018 none MIT — Details →
0.5.0-alpha.e9f96ffe 03 May 2018 none MIT — Details →
0.5.0-alpha.8b905991 02 May 2018 none MIT — Details →
0.5.0-alpha.b4285271 01 May 2018 none MIT — Details →
0.5.0-alpha.7b176463 01 May 2018 none MIT — Details →
0.5.0-alpha.55276695 01 May 2018 none MIT — Details →
0.5.0-alpha.b5bafaeb 23 Apr 2018 none MIT — Details →
0.5.0-alpha.72092d20 08 Apr 2018 none MIT — Details →
0.4.0 08 Apr 2018 none MIT — Details →
0.4.0-alpha.caaefb4c 28 Feb 2018 none MIT — Details →
0.4.0-alpha.f95869d4 28 Feb 2018 none MIT — Details →
0.4.0-alpha.12994a48 26 Feb 2018 none MIT — Details →
0.4.0-alpha.4b14df35 21 Feb 2018 none MIT — Details →
0.4.0-alpha.6546ad11 15 Feb 2018 none MIT — Details →
0.4.0-alpha.15ca1f11 31 Jan 2018 none MIT — Details →
0.3.0 31 Jan 2018 none MIT — Details →
0.3.0-alpha.4143a25b 31 Jan 2018 none MIT — Details →
0.3.0-alpha.71b0b884 20 Jan 2018 none MIT — Details →
0.3.0-alpha.6ceffb8d 19 Jan 2018 none MIT — Details →
0.3.0-alpha.636ae276 19 Jan 2018 none MIT — Details →
0.3.0-alpha.ab81368f 15 Jan 2018 none MIT — Details →
0.3.0-alpha.ac576234 14 Jan 2018 none MIT — Details →
0.3.0-alpha.879f25ec 07 Jan 2018 none MIT — Details →
0.3.0-alpha.5ee3078e 30 Dec 2017 none MIT — Details →
0.3.0-alpha.8857f145 22 Dec 2017 none MIT — Details →
0.3.0-alpha.169f8743 20 Dec 2017 none MIT — Details →
0.3.0-alpha.6ae655c0 20 Dec 2017 none MIT — Details →
0.3.0-alpha.d9c99d3f 20 Dec 2017 none MIT — Details →
0.3.0-alpha.a351eeed 19 Dec 2017 none MIT — Details →
0.3.0-alpha.cf9a0da2 19 Dec 2017 none MIT — Details →
0.3.0-alpha.e6a189cd 19 Dec 2017 none MIT — Details →
0.3.0-alpha.670b24ec 16 Dec 2017 none MIT — Details →
0.3.0-alpha.7f4dc3d4 11 Dec 2017 none MIT — Details →
0.3.0-alpha.033d9ab6 11 Dec 2017 none MIT — Details →
0.3.0-alpha.37064b40 10 Dec 2017 none MIT — Details →
0.3.0-alpha.9a74dfd1 09 Dec 2017 none MIT — Details →
0.3.0-alpha.a7421897 28 Nov 2017 none MIT — Details →
0.3.0-alpha.da60c6b8 28 Nov 2017 none MIT — Details →
0.2.0 14 Aug 2017 none MIT — Details →
0.1.3 13 Jun 2017 none MIT — Details →
0.1.2 23 May 2017 none MIT — Details →
0.1.1 22 May 2017 none MIT — Details →
0.1.0 22 May 2017 none MIT — Details →
0.0.8 03 Mar 2017 none MIT — Details →
0.0.7 08 Feb 2017 none MIT — Details →
0.0.6 17 Jan 2017 none MIT — Details →
0.0.5 21 Nov 2016 none MIT — Details →
0.0.4 31 Oct 2016 none MIT — Details →
0.0.3 20 Sep 2016 none MIT — Details →
0.0.2 31 Aug 2016 none MIT — Details →
0.0.1 26 Aug 2016 none MIT — Details →

All 87 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 babel-plugin-minify-mangle-names

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 babel-plugin-minify-mangle-names

Is babel-plugin-minify-mangle-names safe to use?

Vulert has no vulnerabilities on record for babel-plugin-minify-mangle-names 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 babel-plugin-minify-mangle-names's Vulert package health score?

Vulert scores babel-plugin-minify-mangle-names 60/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 babel-plugin-minify-mangle-names affected?

No. 0.5.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 babel-plugin-minify-mangle-names should I use?

0.5.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 babel-plugin-minify-mangle-names have?

0 vulnerabilities are recorded for babel-plugin-minify-mangle-names 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 babel-plugin-minify-mangle-names vulnerabilities disclosed?

0 vulnerabilities were recorded for babel-plugin-minify-mangle-names 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 babel-plugin-minify-mangle-names 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 babel-plugin-minify-mangle-names for upcoming vulnerabilities?

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