VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

js-beautify: vulnerability history, versions and safety

js-beautify 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 js-beautify vulnerabilities

Vulert verdict on js-beautify 2.0.3 i

Updated on 23 Oct 2026

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

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

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

  • Current release 2.0.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 855 packages i
  • Stars 9,000 i
  • Last release 3 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 js-beautify, 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.0.3 30 Jun 2026 none MIT — Details →
1.15.4 27 Feb 2025 none MIT — Details →
1.15.3 10 Feb 2025 none MIT — Details →
1.15.2 07 Feb 2025 none MIT — Details →
1.15.1 16 Feb 2024 none MIT — Details →
1.15.0 15 Feb 2024 none MIT — Details →
1.14.11 07 Nov 2023 none MIT — Details →
1.14.10 07 Nov 2023 none MIT — Details →
1.14.9 20 Jul 2023 none MIT — Details →
1.14.8 01 Jun 2023 none MIT — Details →
1.14.7 21 Oct 2022 none MIT — Details →
1.14.6 21 Aug 2022 none MIT — Details →
1.14.5 07 Aug 2022 none MIT — Details →
1.14.4 20 Jun 2022 none MIT — Details →
1.14.3 09 Apr 2022 none MIT — Details →
1.14.2 29 Mar 2022 none MIT — Details →
1.14.1 28 Mar 2022 none MIT — Details →
1.14.0 14 Jun 2021 none MIT — Details →
1.13.13 16 Apr 2021 none MIT — Details →
1.13.11 13 Apr 2021 none MIT — Details →
1.13.6 13 Apr 2021 none MIT — Details →
1.13.8 13 Apr 2021 none MIT — Details →
1.13.7 13 Apr 2021 none MIT — Details →
1.13.5 26 Jan 2021 none MIT — Details →
1.13.4 12 Jan 2021 none MIT — Details →
1.13.3 12 Jan 2021 none MIT — Details →
1.13.2 12 Jan 2021 none MIT — Details →
1.13.1 09 Jan 2021 none MIT — Details →
1.13.0 20 Aug 2020 none MIT — Details →
1.12.0 13 Aug 2020 none MIT — Details →
1.11.0 05 Apr 2020 none MIT — Details →
1.10.3 14 Jan 2020 none MIT — Details →
1.10.2 06 Aug 2019 none MIT — Details →
1.10.1 17 Jul 2019 none MIT — Details →
1.10.1-rc2 17 Jul 2019 none MIT — Details →
1.10.0 02 May 2019 none MIT — Details →
1.9.1 25 Mar 2019 none MIT — Details →
1.9.0 28 Feb 2019 none MIT — Details →
1.9.0-beta5 30 Jan 2019 none MIT — Details →
1.9.0-beta4 26 Jan 2019 none MIT — Details →
1.9.0-beta3 18 Jan 2019 none MIT — Details →
1.9.0-beta2 17 Jan 2019 none MIT — Details →
1.9.0-beta1 14 Jan 2019 none MIT — Details →
1.8.10-beta6 13 Jan 2019 none MIT — Details →
1.8.10-beta5 13 Jan 2019 none MIT — Details →
1.8.10-beta4 10 Jan 2019 none MIT — Details →
1.8.10-beta3 08 Jan 2019 none MIT — Details →
1.8.10-beta2 08 Jan 2019 none MIT — Details →
1.8.10-beta1 06 Dec 2018 none MIT — Details →
1.8.9 06 Dec 2018 none MIT — Details →
1.8.8 18 Oct 2018 none MIT — Details →
1.8.7 12 Oct 2018 none MIT — Details →
1.8.6 10 Sep 2018 none MIT — Details →
1.8.5 10 Sep 2018 none MIT — Details →
1.8.4 04 Sep 2018 none MIT — Details →
1.8.3 04 Sep 2018 none MIT — Details →
1.8.3-rc3 01 Sep 2018 none MIT — Details →
1.8.3-rc2 30 Aug 2018 none MIT — Details →
1.8.3-rc1 30 Aug 2018 none MIT — Details →
1.8.1 27 Aug 2018 none MIT — Details →
1.8.0 27 Aug 2018 none MIT — Details →
1.8.0-rc14 23 Aug 2018 none MIT — Details →
1.8.0-rc13 23 Aug 2018 none MIT — Details →
1.8.0-rc12 22 Aug 2018 none MIT — Details →
1.8.0-rc11 20 Aug 2018 none MIT — Details →
1.8.0-rc10 17 Aug 2018 none MIT — Details →
1.8.0-rc9 17 Aug 2018 none MIT — Details →
1.8.0-rc8 16 Aug 2018 none MIT — Details →
1.8.0-rc7 15 Aug 2018 none MIT — Details →
1.8.0-rc6 13 Aug 2018 none MIT — Details →
1.8.0-rc5 12 Aug 2018 none MIT — Details →
1.8.0-rc4 01 Aug 2018 none MIT — Details →
1.8.0-rc3 31 Jul 2018 none MIT — Details →
1.8.0-rc2 07 Jul 2018 none MIT — Details →
1.7.5 07 Dec 2017 none MIT — Details →
1.7.4 09 Oct 2017 none MIT — Details →
1.7.3 18 Sep 2017 none MIT — Details →
1.7.2 18 Sep 2017 none MIT — Details →
1.7.1 18 Sep 2017 none MIT — Details →
1.7.0 18 Sep 2017 none MIT — Details →
1.6.14 12 May 2017 none MIT — Details →
1.6.12 20 Mar 2017 none MIT — Details →
1.6.11 22 Feb 2017 none MIT — Details →
1.6.10 21 Feb 2017 none MIT — Details →
1.6.9 11 Feb 2017 none MIT — Details →
1.6.8 02 Jan 2017 none MIT — Details →
1.6.7 28 Dec 2016 none MIT — Details →
1.6.6 26 Dec 2016 none MIT — Details →
1.6.5 26 Dec 2016 none MIT — Details →
1.6.4 30 Aug 2016 none MIT — Details →
1.6.3 03 Jun 2016 none MIT — Details →
1.6.2 31 Jan 2016 none MIT — Details →
1.6.1 30 Jan 2016 none MIT — Details →
1.6.0 29 Jan 2016 none MIT — Details →
1.5.10 25 Jun 2015 none MIT — Details →
1.5.9 25 Jun 2015 none MIT — Details →
1.5.8 25 Jun 2015 none MIT — Details →
1.5.7 19 Jun 2015 none MIT — Details →
1.5.6 28 May 2015 none MIT — Details →
1.5.5 06 Mar 2015 none MIT — Details →
1.5.4 04 Oct 2014 none — — Details →
1.5.3 02 Oct 2014 none — — Details →
1.5.2 30 Sep 2014 none — — Details →
1.5.1 26 Apr 2014 none — — Details →
1.4.2 08 Nov 2013 none — — Details →
1.4.1 11 Oct 2013 none — — Details →
1.4.0 11 Jun 2013 none — — Details →
1.3.4 03 Jun 2013 none — — Details →
1.3.3 26 May 2013 none — — Details →
1.3.2 30 Apr 2013 none — — Details →
1.3.1 16 Apr 2013 none — — Details →
1.3.0 16 Apr 2013 none — — Details →
1.2.0 27 Mar 2013 none — — Details →
0.4.2 19 Mar 2013 none — — Details →
0.4.1 19 Mar 2013 none — — Details →
0.4.0 19 Mar 2013 none — — Details →
0.3.9 19 Mar 2013 none — — Details →
0.3.8 18 Mar 2013 none — — Details →
0.3.7 18 Mar 2013 none — — Details →
0.3.6 18 Mar 2013 none — — Details →

The newest 120 of 132 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 js-beautify

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 js-beautify

Is js-beautify safe to use?

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

Vulert scores js-beautify 95/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 js-beautify affected?

No. 2.0.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.

Which version of js-beautify should I use?

2.0.3 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 js-beautify have?

0 vulnerabilities are recorded for js-beautify 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 js-beautify vulnerabilities disclosed?

0 vulnerabilities were recorded for js-beautify 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 js-beautify 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 js-beautify for upcoming vulnerabilities?

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