Vulnerability Database · npm · Package report
domain-browser: vulnerability history, versions and safety
domain-browser is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on domain-browser 5.7.0 i
Updated on 23 Oct 2026
Good news: 5.7.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Inactive
What to do: Stay on 5.7.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 5.7.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 5.7.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 1,046 packages i
- Stars 32 i
- OpenSSF scorecard 3/10 i
- Last release 33 months ago i
- Licence Artistic-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 domain-browser, 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.
- 5.7.0-next.1703844645.bc61548e104afd2d3de10f37566a59cd044b8429 29 Dec 2023
- 5.7.0 29 Dec 2023
- 5.6.0 27 Dec 2023
- 5.6.0-next.1703677503.f52d2b7317912fd463dcdcccdafedec9c5a9cd21 27 Dec 2023
- 5.5.0 05 Dec 2023
- 5.5.0-next.1701804711.c0fbc8931f0dca6d65e01ac384c1be2362fcf1a3 05 Dec 2023
- 5.4.0 24 Nov 2023
- 5.4.0-next.1700836136.bbf96458d4e76cc54557a65333d89abd12f1e9eb 24 Nov 2023
- 5.3.0 21 Nov 2023
- 5.3.0-next.1700553759.5235c59b40811afd76c86dca1dd52f46707f6164 21 Nov 2023
- 5.2.0 14 Nov 2023
- 5.2.0-next.1699988186.7a46b2c5089ca5e46ee3e098238ea44d964301d4 14 Nov 2023
- 5.1.0 14 Nov 2023
- 5.1.0-next.1699971443.51d78ce75baf6cabf437c54f02d42c583898ffc5 14 Nov 2023
- 5.0.0-next.1699885938.897e13a73a02a4ffbdbabb8e32bf45b42789359a 13 Nov 2023
- 5.0.0 13 Nov 2023
- 4.23.0 31 Oct 2023
- 4.23.0-next.1698771829.e40ec3d274ff42bb1dc7762b0698a1a21a12e17e 31 Oct 2023
- 4.22.0 29 Jul 2021
- 4.22.0-next.1627591352.4e01e86b5fc27661dd585946578d0625dd4af38d 29 Jul 2021
- 4.21.0 28 Jul 2021
- 4.20.0-next.1627421258.a51dfed94d91423f58ec9f59e71cf1f71be9d4d8 27 Jul 2021
- 4.20.0 27 Jul 2021
- 4.19.0-next.1604239876.eeda285a1a0470ee48d60df8d904f8b47b0997de 01 Nov 2020
- 4.19.0 28 Oct 2020
- 4.19.0-next.1603927694.1ee8a8832eea2ef541bd184b64ed70aa4697874c 28 Oct 2020
- 4.18.0-next.1599393027.c802e4848f1c665b073cb67e5efc27d4063dc1f5 06 Sep 2020
- 4.18.0-next.1599210529.065f6b95a8f50e8a384176f775a1853a2cd341cf 04 Sep 2020
- 4.18.0 04 Sep 2020
- 4.17.0 17 Aug 2020
- 4.17.0-next.1597693394.2525a0f556e0de18027f04d45ceb0a2de2fa29f6 17 Aug 2020
- 4.16.0 04 Aug 2020
- 4.16.0-next.1596513212.5795a9745381a2d5efb76b7d172ae2418ea873cb 04 Aug 2020
- 4.15.0 21 Jul 2020
- 4.14.0 21 Jul 2020
- 4.14.0-next.1595343672.4034b5722d7f4e73f4e57b104ca26a13f0634394 21 Jul 2020
- 4.13.0 03 Jul 2020
- 4.13.0-next.1593752586.a847902f29b90e4a13488eb50e83da9cf2d33466 03 Jul 2020
- 4.12.0 03 Jul 2020
- 4.12.0-next.1593747383.b78cfda33834a5d32e213a0aa920adb2aa2022be 03 Jul 2020
- 4.11.0-next.1593742408.a6c0b2440f684f8994e7268378c2d2c763a0a95c 03 Jul 2020
- 4.11.0 25 Jun 2020
- 4.11.0-next.1593051799.70f3ee4b5aa58c75f8f63922dd1d624e7dfff4c6 25 Jun 2020
- 4.10.0 21 Jun 2020
- 4.10.0-next.1592738253.a76ebb9016346993ef019d898b32ac2d8c71d0c0 21 Jun 2020
- 4.9.0 20 Jun 2020
- 4.9.0-next.1592690379.95472db14cd803e028437108de3ff4b1970f1364 20 Jun 2020
- 4.8.0 19 Jun 2020
- 4.8.0-next.1592606574.c8ac9846ee3b7cf5f1cf6de09e1894a2fd7a361e 19 Jun 2020
- 4.7.0 19 Jun 2020
- 4.7.0-next.1592601838.44ba6c12bce8c142336a541a237788d3d4453d31 19 Jun 2020
- 4.6.0 10 Jun 2020
- 4.6.0-next.1591793210.cbd63bebd15bb6b3710a69ed8b62d16486a32d4a 10 Jun 2020
- 4.5.0 10 Jun 2020
- 4.5.0-next.1591776004.d6a2168a5c04655880d9d748d6f6f5c9cc59c3dc 10 Jun 2020
- 4.4.0 21 May 2020
- 4.4.0-next.1590072000.8a9154e71e23d06a6f9b5a80f5d2ac8618617016 21 May 2020
- 4.3.0 21 May 2020
- 4.3.0-next.1590035244.fe571a8b20fc5099496a25a6924ecdb201123d67 21 May 2020
- 4.2.0 12 May 2020
- 4.2.0-next.1589250196.999957953d58ee5986062a9adc78dfe9e3f74ab3 12 May 2020
- 4.1.0 04 May 2020
- 4.1.0-next.1588595760.aec2e7cec5e1ae1975aaba687f31d9a7d77cbacd 04 May 2020
- 4.0.0-next.1585175705.35e285d185e15fda7ec117d33915f63e24706cb1 25 Mar 2020
- 4.0.0 25 Mar 2020
- 3.5.0 09 Dec 2019
- 3.5.0-next.1575878889.af878d245489557989a75bbc0e8ed1bc8ae22d6b 09 Dec 2019
- 3.4.0 01 Dec 2019
- 3.4.0-next.1575169424.91ac1d9c986aaaa103065ab190fb94a7001a0147 01 Dec 2019
- 3.3.0 30 Nov 2019
- 3.3.0-next.1575145716.3c18f188a9cc5457635a5903ba57c738044b09a7 30 Nov 2019
- 3.2.0 30 Nov 2019
- 3.2.0-next.1575142767.845435bb55b6697013e785a4d576315890c42751 30 Nov 2019
- 3.1.0 30 Nov 2019
- 3.1.0-next.1575142572.b65292dfe20ee7bdf4423c290f3b61b51f035b96 30 Nov 2019
- 3.0.0 30 Nov 2019
- 3.0.0-next.1575140754.e110fd711d32b283d002c7046714e39e453b4571 30 Nov 2019
- 2.0.0-next.1574630902.fc1a8168b8277434656bee6dbf6c762442480e7b 24 Nov 2019
- 2.0.0-next.1574051249.7e249e2d60bff73c856da83c88e69af93e22db11 18 Nov 2019
- 2.0.0-next.1574050827.e77f42e5bb08a270b573797c84f18582e4a07ba8 18 Nov 2019
- 1.2.0 26 Jan 2018
- 1.1.7 12 Dec 2015
- 1.1.6 11 Dec 2015
- 1.1.5 09 Dec 2015
- 1.1.4 03 Feb 2015
- 1.1.3 11 Oct 2014
- 1.1.2 07 Jun 2014
- 1.1.1 27 Dec 2013
- 1.1.0 01 Nov 2013
- 1.0.1 18 Sep 2013
- 1.0.0 18 Sep 2013
All 91 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for domain-browser
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
Questions
About domain-browser
Is domain-browser safe to use?
Vulert has no vulnerabilities on record for domain-browser 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 domain-browser's Vulert package health score?
Vulert scores domain-browser 59/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 domain-browser affected?
No. 5.7.0, 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 domain-browser should I use?
5.7.0 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 domain-browser have?
0 vulnerabilities are recorded for domain-browser 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 domain-browser vulnerabilities disclosed?
0 vulnerabilities were recorded for domain-browser 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 domain-browser 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 domain-browser for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the domain-browser version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.