VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

confusing-browser-globals: vulnerability history, versions and safety

confusing-browser-globals 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 confusing-browser-globals vulnerabilities

Vulert verdict on confusing-browser-globals 1.0.11 i

Updated on 23 Oct 2026

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

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

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

  • Current release 1.0.11 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 65,426 packages i
  • Stars 103,236 i
  • OpenSSF scorecard 3/10 i
  • Last release 58 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 confusing-browser-globals, 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
1.1.0-next.14 12 Apr 2022 none MIT — Details →
1.0.11 14 Dec 2021 none MIT — Details →
2.0.0-next.104 14 Dec 2021 none MIT — Details →
2.0.0-next.103 14 Dec 2021 none MIT — Details →
2.0.0-next.102 08 Dec 2021 none MIT — Details →
2.0.0-next.101 08 Dec 2021 none MIT — Details →
2.0.0-next.91 04 Oct 2021 none MIT — Details →
2.0.0-next.81 01 Sep 2021 none MIT — Details →
2.0.0-next.75 04 Aug 2021 none MIT — Details →
1.0.10 23 Oct 2020 none MIT — Details →
2.0.0-next.300 23 Oct 2020 none MIT — Details →
2.0.0-next.299 23 Oct 2020 none MIT — Details →
2.0.0-next.281 16 Sep 2020 none MIT — Details →
2.0.0-next.279 16 Sep 2020 none MIT — Details →
2.0.0-next.260 05 Aug 2020 none MIT — Details →
2.0.0-next.247 30 Jul 2020 none MIT — Details →
1.1.0-next.103 04 Dec 2019 none MIT — Details →
1.1.0-next.85 14 Nov 2019 none MIT — Details →
1.1.0-next.62 24 Oct 2019 none MIT — Details →
1.1.0-next.61 24 Oct 2019 none MIT — Details →
1.0.9 19 Sep 2019 none MIT — Details →
1.0.8 09 Aug 2019 none MIT — Details →
1.0.7 22 Apr 2019 none MIT — Details →
2.0.0-next.74 17 Apr 2019 none MIT — Details →
2.0.0-next.b0cbf2ca 15 Mar 2019 none MIT — Details →
1.0.6 06 Mar 2019 none MIT — Details →
1.0.6-next.6a95aae9 04 Jan 2019 none MIT — Details →
1.0.5 30 Oct 2018 none MIT — Details →
1.0.5-next.c662dfb0 25 Oct 2018 none MIT — Details →
1.0.5-next.9b4009d7 24 Oct 2018 none MIT — Details →
1.0.4 14 Oct 2018 none MIT — Details →
1.0.3 02 Oct 2018 none MIT — Details →
1.0.2 01 Oct 2018 none MIT — Details →
1.0.1 26 Sep 2018 none MIT — Details →
2.0.0-next.fb6e6f70 25 Sep 2018 none MIT — Details →
2.0.0-next.2150693d 21 Sep 2018 none MIT — Details →
2.0.0-next.a671462c 24 Aug 2018 none MIT — Details →
2.0.0-next.3e165448 18 Jun 2018 none MIT — Details →
2.0.0-next.66cc7a90 21 Apr 2018 none MIT — Details →
2.0.0-next.b2fd8db8 21 Mar 2018 none MIT — Details →
2.0.0-next.47d2d941 07 Feb 2018 none MIT — Details →
2.0.0-next.03604a46 07 Feb 2018 none MIT — Details →
2.0.0-next.9754a231 18 Jan 2018 none MIT — Details →
2.0.0-next.096703ab 18 Jan 2018 none MIT — Details →
0.0.0 14 Jan 2018 none MIT — Details →

All 45 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 confusing-browser-globals

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 confusing-browser-globals

Is confusing-browser-globals safe to use?

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

Vulert scores confusing-browser-globals 66/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 confusing-browser-globals affected?

No. 1.0.11, 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 confusing-browser-globals should I use?

1.0.11 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 confusing-browser-globals have?

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

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

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