VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

browser-sync: vulnerability history, versions and safety

browser-sync 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 browser-sync vulnerabilities

Vulert verdict on browser-sync 3.0.4 i

Updated on 23 Oct 2026

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

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

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

  • Current release 3.0.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 272 packages i
  • Stars 12,291 i
  • OpenSSF scorecard 2/10 i
  • Last release 18 months ago i
  • Licence Apache-2.0 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 browser-sync, 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
3.0.4 02 Apr 2025 none Apache-2.0 — Details →
3.0.3 23 Sep 2024 none Apache-2.0 — Details →
3.0.2 27 Dec 2023 none Apache-2.0 — Details →
3.0.1 27 Dec 2023 none Apache-2.0 — Details →
3.0.0 27 Dec 2023 none Apache-2.0 — Details →
3.0.0-alpha.2 27 Dec 2023 none Apache-2.0 — Details →
3.0.0-alpha.1 27 Dec 2023 none Apache-2.0 — Details →
3.0.0-alpha.0 27 Dec 2023 none Apache-2.0 — Details →
2.30.0-alpha.3 19 May 2023 none Apache-2.0 — Details →
2.30.0-alpha.2 19 May 2023 none Apache-2.0 — Details →
2.30.0-alpha.1 19 May 2023 none Apache-2.0 — Details →
2.29.3 17 May 2023 none Apache-2.0 — Details →
2.29.2 17 May 2023 none Apache-2.0 — Details →
2.29.1 22 Mar 2023 none Apache-2.0 — Details →
2.29.1-alpha.0 22 Mar 2023 none Apache-2.0 — Details →
2.29.0 16 Mar 2023 none Apache-2.0 — Details →
2.28.3 04 Mar 2023 none Apache-2.0 — Details →
2.28.2 04 Mar 2023 none Apache-2.0 — Details →
2.28.1 27 Feb 2023 none Apache-2.0 — Details →
2.28.0 27 Feb 2023 none Apache-2.0 — Details →
2.27.12 23 Feb 2023 none Apache-2.0 — Details →
2.27.11 19 Dec 2022 none Apache-2.0 — Details →
2.27.10 16 May 2022 none Apache-2.0 — Details →
2.27.9 15 Mar 2022 none Apache-2.0 — Details →
2.27.8 13 Mar 2022 none Apache-2.0 — Details →
2.27.7 27 Oct 2021 none Apache-2.0 — Details →
2.27.6 26 Oct 2021 none Apache-2.0 — Details →
2.27.5 27 Jul 2021 none Apache-2.0 — Details →
2.27.4 01 Jul 2021 none Apache-2.0 — Details →
2.27.3 26 Jun 2021 none Apache-2.0 — Details →
2.27.1 24 Jun 2021 none Apache-2.0 — Details →
2.26.14 24 Jan 2021 none Apache-2.0 — Details →
2.26.14-y.2 24 Jan 2021 none Apache-2.0 — Details →
2.26.14-y.1 24 Jan 2021 none Apache-2.0 — Details →
2.26.13 17 Oct 2020 none Apache-2.0 — Details →
2.26.12 26 Jul 2020 none Apache-2.0 — Details →
2.26.10 17 Jul 2020 none Apache-2.0 — Details →
2.26.9 16 Jul 2020 none Apache-2.0 — Details →
2.26.7 07 Jun 2019 none Apache-2.0 — Details →
2.26.6 07 Jun 2019 none Apache-2.0 — Details →
2.26.5 24 Apr 2019 none Apache-2.0 — Details →
2.26.4 22 Apr 2019 none Apache-2.0 — Details →
2.26.3 13 Oct 2018 none Apache-2.0 — Details →
2.26.2 13 Oct 2018 none Apache-2.0 — Details →
2.26.1 13 Oct 2018 none Apache-2.0 — Details →
2.26.0 06 Oct 2018 none Apache-2.0 — Details →
2.25.3-alpha.0 06 Oct 2018 none Apache-2.0 — Details →
2.25.2-alpha.0 06 Oct 2018 none Apache-2.0 — Details →
2.25.1-alpha.0 06 Oct 2018 none Apache-2.0 — Details →
2.25.0 06 Oct 2018 none Apache-2.0 — Details →
2.25.0-alpha.0 17 Sep 2018 none Apache-2.0 — Details →
2.24.7 26 Aug 2018 none Apache-2.0 — Details →
2.24.6 21 Jul 2018 none Apache-2.0 — Details →
2.24.5 24 Jun 2018 none Apache-2.0 — Details →
2.24.4 03 May 2018 none Apache-2.0 — Details →
2.24.3 03 May 2018 none Apache-2.0 — Details →
2.24.3-rc1 02 May 2018 none Apache-2.0 — Details →
2.24.2 02 May 2018 none Apache-2.0 — Details →
2.24.2-rc1 02 May 2018 none Apache-2.0 — Details →
2.24.1 30 Apr 2018 none Apache-2.0 — Details →
2.24.1-rc1 30 Apr 2018 none Apache-2.0 — Details →
2.24.0 29 Apr 2018 none Apache-2.0 — Details →
2.24.0-rc4 29 Apr 2018 none Apache-2.0 — Details →
2.24.0-rc3 29 Apr 2018 none Apache-2.0 — Details →
2.24.0-rc2 29 Apr 2018 none Apache-2.0 — Details →
2.24.0-rc1 29 Apr 2018 none Apache-2.0 — Details →
2.23.7 20 Apr 2018 none Apache-2.0 — Details →
2.23.6 24 Jan 2018 none Apache-2.0 — Details →
2.23.5 10 Jan 2018 none Apache-2.0 — Details →
2.23.4 10 Jan 2018 none Apache-2.0 — Details →
2.23.3 05 Jan 2018 none Apache-2.0 — Details →
2.23.2 01 Jan 2018 none Apache-2.0 — Details →
2.23.1 29 Dec 2017 none Apache-2.0 — Details →
2.23.0 29 Dec 2017 none Apache-2.0 — Details →
2.22.0 28 Dec 2017 none Apache-2.0 — Details →
2.21.0 22 Dec 2017 none Apache-2.0 — Details →
2.20.1 22 Dec 2017 none Apache-2.0 — Details →
2.20.0 21 Dec 2017 none Apache-2.0 — Details →
2.19.0 19 Dec 2017 none Apache-2.0 — Details →
2.18.13 20 Jul 2017 none Apache-2.0 — Details →
2.18.12 21 May 2017 none Apache-2.0 — Details →
2.18.11 15 May 2017 none Apache-2.0 — Details →
2.18.10 15 May 2017 none Apache-2.0 — Details →
2.18.9 15 May 2017 none Apache-2.0 — Details →
2.18.8 13 Feb 2017 none Apache-2.0 — Details →
2.18.7 30 Jan 2017 none Apache-2.0 — Details →
2.18.6 06 Jan 2017 none Apache-2.0 — Details →
2.18.5 11 Dec 2016 none Apache-2.0 — Details →
2.18.4 11 Dec 2016 none Apache-2.0 — Details →
2.18.3 11 Dec 2016 none Apache-2.0 — Details →
2.18.2 20 Nov 2016 none Apache-2.0 — Details →
2.18.1 16 Nov 2016 none Apache-2.0 — Details →
2.18.0 16 Nov 2016 none Apache-2.0 — Details →
2.17.6 13 Nov 2016 none Apache-2.0 — Details →
2.17.5 19 Oct 2016 none Apache-2.0 — Details →
2.17.4 19 Oct 2016 none Apache-2.0 — Details →
2.17.3 12 Oct 2016 none Apache-2.0 — Details →
2.17.2 09 Oct 2016 none Apache-2.0 — Details →
2.17.1 08 Oct 2016 none Apache-2.0 — Details →
2.17.0 30 Sep 2016 none Apache-2.0 — Details →
2.16.1 29 Sep 2016 none — — Details →
2.16.0 14 Sep 2016 none — — Details →
2.15.0 05 Sep 2016 none — — Details →
2.14.3 30 Aug 2016 none — — Details →
2.14.2 30 Aug 2016 none — — Details →
2.14.1 30 Aug 2016 none — — Details →
2.14.0 31 Jul 2016 none — — Details →
2.13.0 07 Jun 2016 none — — Details →
2.12.12 04 Jun 2016 none — — Details →
2.12.11 04 Jun 2016 none — — Details →
2.12.10 27 May 2016 none — — Details →
2.12.9 27 May 2016 none — — Details →
2.12.8 12 May 2016 none — — Details →
2.12.7 10 May 2016 none — — Details →
2.12.6 10 May 2016 none — — Details →
2.12.5 25 Apr 2016 none — — Details →
2.12.4 25 Apr 2016 none — — Details →
2.12.3 13 Apr 2016 none — — Details →
2.12.2 13 Apr 2016 none — — Details →
2.12.1 11 Apr 2016 none — — Details →

The newest 120 of 301 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 browser-sync

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 browser-sync

Is browser-sync safe to use?

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

Vulert scores browser-sync 74/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 browser-sync affected?

No. 3.0.4, 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 browser-sync should I use?

3.0.4 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 browser-sync have?

0 vulnerabilities are recorded for browser-sync 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 browser-sync vulnerabilities disclosed?

0 vulnerabilities were recorded for browser-sync 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 browser-sync 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 browser-sync for upcoming vulnerabilities?

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